io.github.jdhart81/agent-compute-ledger
REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED SEP 20
Compute-is-carbon energy/carbon ledger for agent work with Landauer-limit validation.
Available components
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 Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 694 tokens (~57/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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'
{
"mcpServers": {
"jdhart81-agent-compute-ledger": {
"url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
}
}
} {
"servers": {
"jdhart81-agent-compute-ledger": {
"type": "http",
"url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
}
}
} [mcp_servers.jdhart81-agent-compute-ledger] url = "https://mcp.viridisconservation.com/compute-ledger/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jdhart81-agent-compute-ledger": {
"type": "remote",
"url": "https://mcp.viridisconservation.com/compute-ledger/mcp",
"enabled": true
}
}
} openclaw mcp add jdhart81-agent-compute-ledger --url 'https://mcp.viridisconservation.com/compute-ledger/mcp' --transport streamable-http
mcp_servers:
jdhart81-agent-compute-ledger:
url: "https://mcp.viridisconservation.com/compute-ledger/mcp" {
"McpServers": {
"jdhart81-agent-compute-ledger": {
"Transport": "http",
"Url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
}
}
} assistant mcp add jdhart81-agent-compute-ledger -t streamable-http -u 'https://mcp.viridisconservation.com/compute-ledger/mcp'
{
"mcpServers": {
"jdhart81-agent-compute-ledger": {
"type": "http",
"url": "https://mcp.viridisconservation.com/compute-ledger/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +2
- 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
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 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
- 28 Jul 26 0
- Authorization: unverified → fail ▼ security
- 27 Jul 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
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 20 Sept 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 ~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 ~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 ~13
Fleet-standard self-description.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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 ~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.
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 ~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 ~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 ~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 ~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 ~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 ~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.
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 85 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 12 tools: record_work, footprint, attest, verify_attestation, verify_chain, and 7 more. Their descriptions and schemas cost roughly 675 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.