io.github.jdhart81/agent-compute-ledger
REMOTE · MCP.VIRIDISCONSERVATION.COM
Compute-is-carbon energy/carbon ledger for agent work with Landauer-limit validation.
Available components
Last scanned (23 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 873 tokens (~67/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 3 Nov 26 0
- Tool “attest” changed its title: Attest cosmetic
- Tool “carbon_receipt” changed its title: Carbon receipt cosmetic
- Tool “describe_agent” changed its title: Describe this service cosmetic
- Tool “footprint” changed its title: Footprint cosmetic
- Tool “get_inventory” changed its title: Get inventory cosmetic
- Tool “intelligence_bound” changed its title: Compute the intelligence bound cosmetic
- Tool “list_entries” changed its title: List entries cosmetic
- Tool “list_inventories” changed its title: List inventories cosmetic
- Tool “record_inventory” changed its title: Record inventory cosmetic
- Tool “record_work” changed its title: Record work cosmetic
- Tool “verify_attestation” changed its title: Verify attestation cosmetic
- Tool “verify_chain” changed its title: Verify chain cosmetic
- Tool “verify_inventory_chain” changed its title: Verify inventory chain cosmetic
13 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 2 Nov 26 0
- Schema quality: 60 → 67 ▼ functional
- New tool “intelligence_bound” functional
- 31 Oct 26 0
- Tool “describe_agent” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.viridisconservation.com/compute-ledger/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.viridisconservation.com | CN=YE1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5abb43a3acf241ca07b1eb9ff25cafac4e4 |
| SANs: mcp.viridisconservation.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.viridisconservation.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| viridisconservation.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.viridisconservation.com/compute-ledger/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/compute-ledger/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/compute-ledger/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attest Attest ~38
Issue a content-addressed attestation for a ledger entry (verifiable green-compute / energy claim).
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
carbon_receipt Carbon receipt ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | – |
| offset_ref | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent Describe this service ~49
Describe this agent: name, version, purpose, every action it supports and the inputs each one takes. Read-only and free; call it first to learn how to use this server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
footprint Footprint ~52
Aggregate footprint for an agent: total J, kWh, gCO2e, cost, and mean Landauer efficiency. Totals are exact sums of the ledger entries.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_inventory Get inventory ~25
Fetch one immutable inventory record by inventory_id.
| Name | Type | Req | Description |
|---|---|---|---|
| inventory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
intelligence_bound Compute the intelligence bound ~143
Thermodynamic ceiling on information processing for a power budget. Returns the Landauer ceiling P / (k_B*T*ln 2) on irreversible bit operations per second (established physics), the Intelligence Bound min(rho*B, P / (k_B*T*ln 2)) (Viridis's working conjecture), which term binds, and, if you pass a measured rate, how far your workload sits below it. Free, read-only and deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| bandwidth_bits_per_s | – | – | – |
| measured_bits_per_s | – | – | – |
| power_w | number | yes | – |
| temperature_k | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_entries List entries ~24
List all ledger entries for an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_inventories List inventories ~29
List the separate GHG inventory chain for an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
record_inventory Record inventory ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| content_digest | string | yes | – |
| factor_pack_digest | string | yes | – |
| factor_pack_version | string | yes | – |
| inventory_id | string | yes | – |
| mass_g | integer | yes | – |
| source_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
record_work Record work ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| bit_ops | – | – | – |
| duration_s | number | yes | – |
| entry_id | string | yes | – |
| grid_intensity_g_per_kwh | number | – | – |
| power_w | number | yes | – |
| price_minor_per_kwh | – | – | – |
| task | string | – | – |
| temperature_k | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_attestation Verify attestation ~29
Verify an attestation by recomputing the entry hash.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_chain Verify chain ~31
Verify the tamper-evident hash chain of an agent's ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_inventory_chain Verify inventory chain ~29
Verify an agent's inventory hash chain independently of compute work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.jdhart81/agent-compute-ledger MCP server?
io.github.jdhart81/agent-compute-ledger is a hosted endpoint at https://mcp.viridisconservation.com/compute-ledger/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.viridisconservation.com
claude mcp add --transport http jdhart81-agent-compute-ledger 'https://mcp.viridisconservation.com/compute-ledger/mcp'
What is the io.github.jdhart81/agent-compute-ledger MCP server?
io.github.jdhart81/agent-compute-ledger is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-compute-ledger. Compute-is-carbon energy/carbon ledger for agent work with Landauer-limit validation. This page covers its hosted endpoint (https://mcp.viridisconservation.com/compute-ledger/mcp).
Is the io.github.jdhart81/agent-compute-ledger MCP server safe to use?
io.github.jdhart81/agent-compute-ledger scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jdhart81/agent-compute-ledger MCP server expose?
io.github.jdhart81/agent-compute-ledger exposes 13 tools: record_work, footprint, attest, verify_attestation, verify_chain, and 8 more. Their descriptions and schemas cost roughly 854 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-compute-ledger MCP server require authentication?
Yes. io.github.jdhart81/agent-compute-ledger asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.jdhart81/agent-compute-ledger MCP server still maintained?
io.github.jdhart81/agent-compute-ledger is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.