io.github.jdhart81/agent-offset-clearinghouse
REMOTE · MCP.VIRIDISCONSERVATION.COM
Verified conservation credits matched to agent compute emissions — the conservation flywheel of the
Available components
Last scanned (22 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1429 tokens (~75/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
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.
- 3 Nov 26 0
- Tool “book” changed its title: Book cosmetic
- Tool “buy_offset” changed its title: Buy offset cosmetic
- Tool “buy_offset_budget” changed its title: Buy offset budget cosmetic
- Tool “certify_disbursement” changed its title: Certify disbursement cosmetic
- Tool “delist_credit” changed its title: Delist credit cosmetic
- Tool “describe_agent” changed its title: Describe this service cosmetic
- Tool “disbursement_schedule” changed its title: Disbursement schedule cosmetic
- Tool “get_purchase” changed its title: Get purchase cosmetic
- Tool “list_credit” changed its title: List credit cosmetic
- Tool “list_projects” changed its title: List projects cosmetic
- Tool “net_position” changed its title: Net position cosmetic
- Tool “project_funding” changed its title: Project funding cosmetic
- Tool “register_project” changed its title: Register project cosmetic
- Tool “settlement_batch” changed its title: Settlement batch cosmetic
- Tool “verify_certificate” changed its title: Verify certificate cosmetic
- Tool “verify_disbursement” changed its title: Verify disbursement cosmetic
- Tool “verify_retirement” changed its title: Verify retirement cosmetic
- Tool “verra_retirement_record” changed its title: Verra retirement record cosmetic
- Tool “verra_supply” changed its title: Verra supply cosmetic
19 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 Oct 26 +1
- 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
- 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
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/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 |
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 →
book Book ~21
The full credit book with per-credit and book-wide mass conservation totals.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
buy_offset 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.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | yes | – |
| dry_run | boolean | – | – |
| mass_g | integer | yes | – |
| purchase_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
buy_offset_budget 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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_minor | integer | yes | – |
| buyer | string | yes | – |
| dry_run | boolean | – | – |
| purchase_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
certify_disbursement 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.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delist_credit 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.
| Name | Type | Req | Description |
|---|---|---|---|
| credit_id | string | yes | – |
| reason | string | yes | – |
| 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.
disbursement_schedule 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).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_purchase Get purchase ~26
Fetch a past purchase / offset certificate by id.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_credit 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.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | string | yes | – |
| mass_g | integer | yes | – |
| methodology | string | – | – |
| price_minor_per_kg | integer | yes | – |
| project_id | string | yes | – |
| registry | string | – | – |
| serial_number | string | – | – |
| vcs_project_id | string | – | – |
| verification_ref | string | yes | – |
| vintage | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_projects List projects ~17
List all registered restoration projects with their metadata.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
net_position Net position ~51
Buyer's carbon position: emitted (from agent-compute-ledger) minus retired. carbon_accountable == true when fully offset.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | yes | – |
| emitted_g | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
project_funding 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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
register_project 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.
| Name | Type | Req | Description |
|---|---|---|---|
| beneficiary | string | – | – |
| location | string | – | – |
| methodology | string | – | – |
| name | string | – | – |
| project_id | string | yes | – |
| registry_ref | string | – | – |
| verification_ref | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
settlement_batch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | yes | – |
| since | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_certificate Verify certificate ~29
Verify an offset certificate: recompute its hash and check the ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_disbursement 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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_retirement 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.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_id | string | yes | – |
| required_g | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verra_retirement_record 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).
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_id | string | yes | – |
| retirement_reason | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verra_supply 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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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
claude mcp add --transport http jdhart81-agent-offset-clearinghouse 'https://mcp.viridisconservation.com/offsets/mcp'
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 86 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,408 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.