io.github.jdhart81/agent-surety
REMOTE · MCP.VIRIDISCONSERVATION.COM
Counterparty risk transfer for the agent economy: agents post bonds behind their promises, wronged c
Available components
Last scanned (7 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 678 tokens (~67/item across 10 items; 10 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 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 “activate_bond” changed its title: Activate bond cosmetic
- Tool “bond_status” changed its title: Bond status cosmetic
- Tool “describe_agent” changed its title: Describe this service cosmetic
- Tool “file_claim” changed its title: File claim cosmetic
- Tool “list_bonds” changed its title: List bonds cosmetic
- Tool “post_bond” changed its title: Post bond cosmetic
- Tool “price_bond” changed its title: Price bond cosmetic
- Tool “release_bond” changed its title: Release bond cosmetic
- Tool “slash_bond” changed its title: Slash bond cosmetic
- Tool “verify_audit” changed its title: Verify audit cosmetic
10 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 Oct 26 +2
- Tool “release_bond” is now declared destructive security
- Tool “slash_bond” is now declared destructive security
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- 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 5 Nov 2026 · Probed https://mcp.viridisconservation.com/surety/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/surety/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/surety/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/surety/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 →
activate_bond Activate bond ~50
Mark a POSTED bond ACTIVE (idempotent). funding_ref links the payment rail transaction that funded the stake.
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
| funding_ref | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
bond_status Bond status ~31
Current record for a bond (state, balances, claims, audit head).
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent Describe this service ~14
Return capabilities and input contract.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
file_claim File claim ~65
File a claim against an ACTIVE bond. Claims pay out ONLY when an arbitration ruling upholds them (see slash_bond).
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | – |
| bond_id | string | yes | – |
| claimant | string | yes | – |
| reason | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_bonds List bonds ~38
List bonds, optionally filtered by state (POSTED|ACTIVE|RELEASED|EXHAUSTED).
| Name | Type | Req | Description |
|---|---|---|---|
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
post_bond Post bond ~96
Post a surety bond behind an agent's promises. principal is a positive integer in minor units; expires_at is the ISO-8601 coverage window end. The bond fee (2% default) is computed and frozen at post.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | – | – |
| currency | string | – | – |
| expires_at | string | yes | – |
| principal | integer | yes | – |
| principal_agent | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
price_bond Price bond ~147
Underwrite a surety bond: deterministic actuarial premium quote from a counterparty's track record (attestations, notarized deliveries, completed bonds lower the rate; slashes raise it or decline outright). Integer-only model uw-v1; the returned quote_hash lets any party recompute and verify the quote. Pure — never mutates bond state.
| Name | Type | Req | Description |
|---|---|---|---|
| attestations | integer | – | – |
| bonds_completed | integer | – | – |
| coverage_minor | integer | yes | – |
| duration_days | integer | yes | – |
| slashed_minor | integer | – | – |
| slashes | integer | – | – |
| successful_deliveries | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
release_bond Release bond ~41
Release the remaining stake to the principal after the coverage window elapses — refused while any claim is still open.
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
slash_bond Slash bond ~109
Execute an arbitration ruling against a claim. Requires the ruling's case id + content hash from agent-arbitration — no ruling, no slash; a given ruling pays at most once. Payout caps at the bond's available balance (over-claims exhaust the bond).
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
| claim_id | string | yes | – |
| ruling_case_id | string | yes | – |
| ruling_hash | string | yes | – |
| upheld | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_audit Verify audit ~31
Validate the tamper-evident audit hash chain for a bond.
| Name | Type | Req | Description |
|---|---|---|---|
| bond_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.jdhart81/agent-surety MCP server?
io.github.jdhart81/agent-surety is a hosted endpoint at https://mcp.viridisconservation.com/surety/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-surety 'https://mcp.viridisconservation.com/surety/mcp'
What is the io.github.jdhart81/agent-surety MCP server?
io.github.jdhart81/agent-surety is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-surety. Counterparty risk transfer for the agent economy: agents post bonds behind their promises, wronged c. This page covers its hosted endpoint (https://mcp.viridisconservation.com/surety/mcp).
Is the io.github.jdhart81/agent-surety MCP server safe to use?
io.github.jdhart81/agent-surety 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-surety MCP server expose?
io.github.jdhart81/agent-surety exposes 10 tools: post_bond, activate_bond, file_claim, slash_bond, release_bond, and 5 more. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-surety MCP server require authentication?
Yes. io.github.jdhart81/agent-surety 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-surety MCP server still maintained?
io.github.jdhart81/agent-surety is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.