Is the Jdhart81 Agent Offset Clearinghouse MCP server down?

mcp-registry/io.github.jdhart81/agent-offset-clearinghouse · v1.28.1

healthy
Last checked 2026-10-17 07:33 UTC · handshake 983ms

As of 2026-10-17 07:33 UTC, the Jdhart81 Agent Offset Clearinghouse MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
3,549
outages (90d)
6
tools
32

Verified conservation credits matched to agent compute emissions — the conservation flywheel of the

Install Jdhart81 Agent Offset Clearinghouse MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http jdhart81-agent-offset-clearinghouse-mcp- https://mcp.viridisconservation.com/offsets/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "jdhart81-agent-offset-clearinghouse-mcp-": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/offsets/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 3 warning(s) across 19 tool(s); ~2,611 tokens of tool definitions.
Scores higher than 9% of 15,262 MCP servers Glimind has audited.
Its tool list costs an agent ~2,611 tokens per session — more than 50% of servers.
no tool-poisoning patterns
Schemas100
Descriptions38
Safety hints3
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (3)

19 of 19 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: book, buy_offset, buy_offset_budget, certify_disbursement, delist_credit and 14 more

40 parameter(s) across 14 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: buy_offset, buy_offset_budget, certify_disbursement, delist_credit, disbursement_schedule and 9 more

4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: book, buy_offset, buy_offset_budget, settlement_batch

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 14 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jdhart81%2Fagent-offset-clearinghouse/fixes

book 1 change
{
  "name": "book",
  "description": "The full credit book with per-credit and book-wide mass conservation totals.",
  "inputSchema": {
    "type": "object",
    "title": "bookArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
buy_offset 1 change
{
  "name": "buy_offset",
  "description": "Retire mass_g of verified credits for a buyer: cheapest-first matching,\n    exactly-once (idempotent on purchase_id), returns a content-addressed\n    offset certificate with per-fill costs. Payment settles via escrow.\n    dry_run=true previews the exact fills/cost without mutating the book.",
  "inputSchema": {
    "type": "object",
    "title": "buy_offsetArguments",
    "required": [
      "buyer",
      "purchase_id",
      "mass_g"
    ],
    "properties": {
      "buyer": {
        "type": "string",
        "title": "Buyer"
      },
      "mass_g": {
        "type": "integer",
        "title": "Mass G"
      },
      "dry_run": {
        "type": "boolean",
        "title": "Dry Run",
        "default": false
      },
      "purchase_id": {
        "type": "string",
        "title": "Purchase Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
buy_offset_budget 1 change
{
  "name": "buy_offset_budget",
  "description": "Money-denominated offset purchase: retire the maximum cheapest-first\n    verified mass whose exact cost fits inside budget_minor (never overspends).\n    Built for callers whose restoration obligation is a currency amount —\n    e.g. a revenue share accrued in a ledger. Idempotent on purchase_id;\n    dry_run=true previews without mutating.",
  "inputSchema": {
    "type": "object",
    "title": "buy_offset_budgetArguments",
    "required": [
      "buyer",
      "purchase_id",
      "budget_minor"
    ],
    "properties": {
      "buyer": {
        "type": "string",
        "title": "Buyer"
      },
      "dry_run": {
        "type": "boolean",
        "title": "Dry Run",
        "default": false
      },
      "purchase_id": {
        "type": "string",
        "title": "Purchase Id"
      },
      "budget_minor": {
        "type": "integer",
        "title": "Budget Minor"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jdhart81/agent-offset-clearinghouse"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jdhart81/agent-offset-clearinghouse"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-offset-clearinghouse.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-offset-clearinghouse?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-offset-clearinghouse?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-offset-clearinghouse.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-offset-clearinghouse.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-offset-clearinghouse?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8a999b81ae0d6505…, first seen 2026-10-17, included at leaf 1992 of 17,132. Version history · verify what your client received.

Tools (32)

Compare: most reliable other servers · most reliable data servers · most reliable security servers · most reliable finance servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Jdhart81 Agent Offset Clearinghouse MCP server down right now?

As of 2026-10-17 07:33 UTC, the Jdhart81 Agent Offset Clearinghouse MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Jdhart81 Agent Offset Clearinghouse MCP server provide?

Jdhart81 Agent Offset Clearinghouse MCP server advertises 32 tools, including agent-arbitration, agent-compute-ledger, agent-covenant, agent-escrow, agent-identity-registry.

How do I install Jdhart81 Agent Offset Clearinghouse MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.viridisconservation.com/offsets/mcp

Is the Jdhart81 Agent Offset Clearinghouse MCP server safe to connect to an AI agent?

Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Jdhart81 Agent Offset Clearinghouse MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.