mcpbeat

Agent Compute Ledger MCP Server

io.github.jdhart81/agent-compute-ledger
answering

Agent Compute Ledger is answering right now. Last checked 3 min ago. It exposes 12 tools. Last commit 3 Aug 2026.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
357 ms
Response time
average over 24h
0
Stars
last commit 3 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add agent-compute-ledger --transport http https://mcp.viridisconservation.com/compute-ledger/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agent-compute-ledger": {
      "url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agent-compute-ledger]
url = "https://mcp.viridisconservation.com/compute-ledger/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-compute-ledger": {
      "url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agent-compute-ledger": {
      "url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
verify_attestation
Verify an attestation by recomputing the entry hash.
verify_chain
Verify the tamper-evident hash chain of an agent's ledger.
verify_inventory_chain
Verify an agent's inventory hash chain independently of compute work.
record
record_inventory
Record an audited GHG inventory in a separate append-only chain. mass_g is exact integer grams; content and factor-pack digests are bare lowercase SHA-256 hex. Idempotent on inventory_id.
record_work
Record a unit of agent compute work. energy_j = power_w * duration_s; carbon_g follows from grid intensity. If bit_ops is declared, the entry is validated against the Landauer floor (bit_ops * kB * T * ln2) — physically impossible claims are rejected. Idempotent on entry_id.
attest
attest
Issue a content-addressed attestation for a ledger entry (verifiable green-compute / energy claim).
carbon
carbon_receipt
Emit an x402-C carbon receipt for a recorded work entry — the physically-grounded {version, g_co2e, energy_j, method, landauer_*, ...} object an x402 machine-payment receipt can carry. method is 'landauer-floor' when the workload declared bit_ops (thermodynamically validated), else 'measured'. Pass offset_ref (a retirement id from the offset clearinghouse) to assert carbon-neutrality. Read-only; the returned attestation_hash binds the receipt to the ledger's hash chain.
describe
describe_agent
Fleet-standard self-description.
entries
list_entries
List all ledger entries for an agent.
footprint
footprint
Aggregate footprint for an agent: total J, kWh, gCO2e, cost, and mean Landauer efficiency. Totals are exact sums of the ledger entries.
inventories
list_inventories
List the separate GHG inventory chain for an agent.
inventory
get_inventory
Fetch one immutable inventory record by inventory_id.

Endpoints

URLTransportStateLatencyChecked
https://mcp.viridisconservation.com/compute-ledger/mcp streamable-http answering 384 ms 3 min ago

Agent Compute Ledger — questions

Answers built from our own checks of this server.

What can Agent Compute Ledger do?
It exposes 12 tools, read directly from the server on our last check. Among them: attest, carbon_receipt, describe_agent, footprint, get_inventory, list_entries and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Agent Compute Ledger mostly used for?
Its tools cluster around verify and record. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Agent Compute Ledger working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 357 ms. The bar chart above shows every period we have measured.
How do I connect Agent Compute Ledger?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Compute Ledger need an API key?
No. Agent Compute Ledger completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Compute Ledger?
It answers our handshake in 357 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Agent Compute Ledger open source?
Yes — written in Python, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.