Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.jdhart81/agent-offset-clearinghouse

REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED SEP 20

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

Available components

remote · mcp.viridisconservation.com 85
0 this week 85 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1393 tokens (~73/item across 19 items; 19 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 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 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
Install

How do I install the io.github.jdhart81/agent-offset-clearinghouse MCP server?

io.github.jdhart81/agent-offset-clearinghouse is a hosted endpoint at https://mcp.viridisconservation.com/offsets/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

# add to Claude Code
claude mcp add --transport http jdhart81-agent-offset-clearinghouse 'https://mcp.viridisconservation.com/offsets/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "jdhart81-agent-offset-clearinghouse": {
      "url": "https://mcp.viridisconservation.com/offsets/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jdhart81-agent-offset-clearinghouse": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/offsets/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.jdhart81-agent-offset-clearinghouse]
url = "https://mcp.viridisconservation.com/offsets/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jdhart81-agent-offset-clearinghouse": {
      "type": "remote",
      "url": "https://mcp.viridisconservation.com/offsets/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jdhart81-agent-offset-clearinghouse --url 'https://mcp.viridisconservation.com/offsets/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jdhart81-agent-offset-clearinghouse:
    url: "https://mcp.viridisconservation.com/offsets/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jdhart81-agent-offset-clearinghouse": {
      "Transport": "http",
      "Url": "https://mcp.viridisconservation.com/offsets/mcp"
    }
  }
}
# add to Vellum
assistant mcp add jdhart81-agent-offset-clearinghouse -t streamable-http -u 'https://mcp.viridisconservation.com/offsets/mcp'
// mcp.json
{
  "mcpServers": {
    "jdhart81-agent-offset-clearinghouse": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/offsets/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 +1
    • 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
  • 30 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
Diagnostics

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/offsets/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/offsets/mcp Verified 200
http (plaintext) http://mcp.viridisconservation.com/offsets/mcp HTTPS enforced 308 https://mcp.viridisconservation.com/offsets/mcp
MCP tools · 19 exposed · ~1,372 tokens

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 →

Tool Tokens
book ~21

The full credit book with per-credit and book-wide mass conservation totals.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

buy_offset ~101

Retire mass_g of verified credits for a buyer: cheapest-first matching, exactly-once (idempotent on purchase_id), returns a content-addressed offset certificate with per-fill costs. Payment settles via escrow. dry_run=true previews the exact fills/cost without mutating the book.

NameTypeReqDescription
buyerstringyes–
dry_runboolean––
mass_gintegeryes–
purchase_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

buy_offset_budget ~108

Money-denominated offset purchase: retire the maximum cheapest-first verified mass whose exact cost fits inside budget_minor (never overspends). Built for callers whose restoration obligation is a currency amount — e.g. a revenue share accrued in a ledger. Idempotent on purchase_id; dry_run=true previews without mutating.

NameTypeReqDescription
budget_minorintegeryes–
buyerstringyes–
dry_runboolean––
purchase_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

certify_disbursement ~92

Freeze the current disbursement schedule into a certified, tamper-evident batch (content-addressed, hash-chained). Idempotent on batch_id; only newly-accrued proceeds for verified projects are certified (never disbursed twice). This is the certified investment record the CEO executes the actual Stripe transfers against.

NameTypeReqDescription
batch_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

delist_credit ~66

Admin operation: remove a credit from the active fill path while retaining its listing and retirement history for audit. Idempotent for an already-delisted credit. Gateway state-change authentication is required.

NameTypeReqDescription
credit_idstringyes–
reasonstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

describe_agent ~13

Fleet-standard self-description.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

disbursement_schedule ~91

Automated disbursement preview: for each verified restoration project, splits its newly-accrued proceeds into the Viridis Conservation withhold (default 15%, seeds the software/business) and the project payout (85%). Read-only. Funded-but-unregistered projects are surfaced separately as pending_registration (can't pay an unverified project).

NameTypeReqDescription
project_idstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_purchase ~26

Fetch a past purchase / offset certificate by id.

NameTypeReqDescription
purchase_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_credit ~173

List a conservation credit on the book. verification_ref (a D-Score / land-verification attestation) is REQUIRED — unverified credits cannot enter the book. To trade on the Verra network, pass registry="verra" with the VCS provenance (vcs_project_id, serial_number, vintage, methodology) so retirements are cross-referenceable on registry.verra.org.

NameTypeReqDescription
issuerstringyes–
mass_gintegeryes–
methodologystring––
price_minor_per_kgintegeryes–
project_idstringyes–
registrystring––
serial_numberstring––
vcs_project_idstring––
verification_refstringyes–
vintagestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_projects ~17

List all registered restoration projects with their metadata.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

net_position ~51

Buyer's carbon position: emitted (from agent-compute-ledger) minus retired. carbon_accountable == true when fully offset.

NameTypeReqDescription
buyerstringyes–
emitted_gnumberyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

project_funding ~82

Supply-side disbursement ledger: how much each restoration project has earned from retirements and is owed (gross_proceeds_minor + retired_g). Pass a project_id for one project, else all. Read-only — the CEO settles the actual payout. This is what makes the clearinghouse fund restoration.

NameTypeReqDescription
project_idstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

register_project ~109

Register a VERIFIED restoration project so retirements against its credits can be funded. verification_ref (D-Score / land-verification / registry id) is required — only verified conservation is funded. project_id is immutable once registered.

NameTypeReqDescription
beneficiarystring––
locationstring––
methodologystring––
namestring––
project_idstringyes–
registry_refstring––
verification_refstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

settlement_batch ~74

Read-only cash-settlement summary for a buyer: the list + exact sums (purchases, mass_g, cost_minor) of their retirements, optionally since an ISO-8601 timestamp — the statement a human settles in one transfer.

NameTypeReqDescription
buyerstringyes–
sincestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_certificate ~29

Verify an offset certificate: recompute its hash and check the ledger.

NameTypeReqDescription
certificateobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_disbursement ~41

Recompute the disbursement certificate hash chain and confirm whole-book conservation of disbursed proceeds. Any party can audit disbursements.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

verify_retirement ~92

x402-C C4 check: confirm a retirement (offset_ref = purchase_id) actually retires at least required_g grams of verified conservation credit — the check that lets a carbon receipt's neutrality claim be honored. Returns covered / retired_g / shortfall_g and the backing credits. Read-only.

NameTypeReqDescription
purchase_idstringyes–
required_ginteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

verra_retirement_record ~118

Generate the Verra-portal-ready retirement record(s) for a retirement made against Verra supply — VCS project id, serial, vintage, methodology, quantity (tCO2e), beneficiary, and the registry.verra.org cross-reference. Read-only. Submit these under the Viridis Verra account to finalize the on-registry retirement (portal today; auto-posts when Verra's transaction API is live).

NameTypeReqDescription
purchase_idstringyes–
retirement_reasonstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

verra_supply ~68

The tradeable Verra VCS book: verified credits carrying genuine Verra provenance (project id + serial + vintage), cross-referenceable on registry.verra.org. Read-only. Every retirement nets the project 85% and Viridis the 15% marketplace take.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the io.github.jdhart81/agent-offset-clearinghouse MCP server?

io.github.jdhart81/agent-offset-clearinghouse is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-offset-clearinghouse. Verified conservation credits matched to agent compute emissions, the conservation flywheel of the. This page covers its hosted endpoint (https://mcp.viridisconservation.com/offsets/mcp).

Is the io.github.jdhart81/agent-offset-clearinghouse MCP server safe to use?

io.github.jdhart81/agent-offset-clearinghouse 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-offset-clearinghouse MCP server expose?

io.github.jdhart81/agent-offset-clearinghouse exposes 19 tools: list_credit, delist_credit, verra_supply, verra_retirement_record, buy_offset, and 14 more. Their descriptions and schemas cost roughly 1,372 tokens of context every time the server is loaded.

Does the io.github.jdhart81/agent-offset-clearinghouse MCP server require authentication?

Yes. io.github.jdhart81/agent-offset-clearinghouse 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-offset-clearinghouse MCP server still maintained?

io.github.jdhart81/agent-offset-clearinghouse 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.