io.github.jdhart81/agent-arbitration
REMOTE · MCP.VIRIDISCONSERVATION.COM
Deterministic, machine-verifiable dispute resolution for A2A escrows.
Available components
Last scanned (9 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 414 tokens (~51/item across 8 items; 8 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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 “describe_agent” changed its title: Describe this service cosmetic
- Tool “file_case” changed its title: File case cosmetic
- Tool “get_case” changed its title: Get case cosmetic
- Tool “list_cases” changed its title: List cases cosmetic
- Tool “rule” changed its title: Rule cosmetic
- Tool “set_trust_scores” changed its title: Set trust scores cosmetic
- Tool “submit_evidence” changed its title: Submit evidence cosmetic
- Tool “verify_ruling” changed its title: Verify ruling cosmetic
8 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 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
- 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/arbitration/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/arbitration/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/arbitration/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/arbitration/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 →
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.
file_case File case ~67
File a dispute over an escrow. Opens the evidence window. Parties must be distinct; amount is in minor currency units (cents).
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | – |
| claimant | string | yes | – |
| escrow_id | string | yes | – |
| respondent | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_case Get case ~26
Fetch the full case record, including any ruling.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cases List cases ~32
List cases, optionally filtered by state (FILED|EVIDENCE_OPEN|RULED).
| Name | Type | Req | Description |
|---|---|---|---|
| state | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
rule Rule ~62
Issue the deterministic ruling: allocates 100% of the disputed amount from evidence weights + trust scores, and emits an escrow instruction (release/refund). Exactly-once — re-ruling returns the existing ruling.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_trust_scores Set trust scores ~43
Attach trust-oracle reputation scores (party -> [0,1]) as ruling inputs.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| scores | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_evidence Submit evidence ~73
Submit evidence while the case is open. kind: delivery_proof (weight 3), log (2), or statement (1). Only the named parties may submit.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| content | string | – | – |
| kind | string | yes | – |
| party | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_ruling Verify ruling ~43
Recompute the ruling from its cited evidence + trust inputs and check it matches the stored allocation (machine-checkable justice).
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.jdhart81/agent-arbitration MCP server?
io.github.jdhart81/agent-arbitration is a hosted endpoint at https://mcp.viridisconservation.com/arbitration/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-arbitration 'https://mcp.viridisconservation.com/arbitration/mcp'
What is the io.github.jdhart81/agent-arbitration MCP server?
io.github.jdhart81/agent-arbitration is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-arbitration. Deterministic, machine-verifiable dispute resolution for A2A escrows. This page covers its hosted endpoint (https://mcp.viridisconservation.com/arbitration/mcp).
Is the io.github.jdhart81/agent-arbitration MCP server safe to use?
io.github.jdhart81/agent-arbitration 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-arbitration MCP server expose?
io.github.jdhart81/agent-arbitration exposes 8 tools: file_case, submit_evidence, set_trust_scores, rule, verify_ruling, and 3 more. Their descriptions and schemas cost roughly 395 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-arbitration MCP server require authentication?
Yes. io.github.jdhart81/agent-arbitration 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-arbitration MCP server still maintained?
io.github.jdhart81/agent-arbitration 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.