Is the Jdhart81 Agent Compute Ledger MCP server down?

mcp-registry/io.github.jdhart81/agent-compute-ledger · v1.28.1

healthy
Last checked 2026-10-19 08:53 UTC · handshake 222ms

As of 2026-10-19 08:53 UTC, the Jdhart81 Agent Compute Ledger MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
99.9%
checks observed
3,837
outages (90d)
8
tools
25

Compute-is-carbon energy/carbon ledger for agent work with Landauer-limit validation.

Install Jdhart81 Agent Compute Ledger MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http jdhart81-agent-compute-ledger-mcp-server https://mcp.viridisconservation.com/compute-ledger/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "jdhart81-agent-compute-ledger-mcp-server": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
    }
  }
}

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

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 2 warning(s) across 12 tool(s); ~1,413 tokens of tool definitions.
Scores higher than 14% of 15,353 MCP servers Glimind has audited.
Its tool list costs an agent ~1,413 tokens per session — lighter than 60% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (2)

12 of 12 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. How to fix →

Tools: attest, carbon_receipt, describe_agent, footprint, get_inventory and 7 more

26 parameter(s) across 11 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. How to fix →

Tools: attest, carbon_receipt, footprint, get_inventory, list_entries and 6 more

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 11 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-compute-ledger/fixes

describe_agent 1 change 
{
  "name": "describe_agent",
  "description": "Fleet-standard self-description.",
  "inputSchema": {
    "type": "object",
    "title": "describe_agentArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_inventory 1 change 
{
  "name": "get_inventory",
  "description": "Fetch one immutable inventory record by inventory_id.",
  "inputSchema": {
    "type": "object",
    "title": "get_inventoryArguments",
    "required": [
      "inventory_id"
    ],
    "properties": {
      "inventory_id": {
        "type": "string",
        "title": "Inventory Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_entries 1 change 
{
  "name": "list_entries",
  "description": "List all ledger entries for an agent.",
  "inputSchema": {
    "type": "object",
    "title": "list_entriesArguments",
    "required": [
      "agent_id"
    ],
    "properties": {
      "agent_id": {
        "type": "string",
        "title": "Agent Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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-compute-ledger"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jdhart81/agent-compute-ledger"}) 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-compute-ledger.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-compute-ledger?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-compute-ledger?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-compute-ledger.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-compute-ledger.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-compute-ledger?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:910452224562140f…, first seen 2026-10-17, included at leaf 239 of 25,815. Version history · verify what your client received.

Tools (25)

Compare: most reliable other servers · most reliable security servers · most reliable finance servers · most reliable identity servers · most reliable metering 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 Compute Ledger MCP server down right now?

As of 2026-10-19 08:53 UTC, the Jdhart81 Agent Compute Ledger MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Jdhart81 Agent Compute Ledger MCP server provide?

Jdhart81 Agent Compute Ledger MCP server advertises 25 tools, including agent-arbitration, agent-compute-ledger, agent-covenant, agent-escrow, agent-identity-registry.

How do I install Jdhart81 Agent Compute Ledger MCP server?

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

Is the Jdhart81 Agent Compute Ledger MCP server safe to connect to an AI agent?

Glimind scanned all 12 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 Compute Ledger 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.

Feedback
Help us improve