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-arbitration

REMOTE · MCP.VIRIDISCONSERVATION.COM · SCANNED SEP 20

Deterministic, machine-verifiable dispute resolution for A2A escrows.

Available components

remote · mcp.viridisconservation.com 84
0 this week 84 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 Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 378 tokens (~47/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
Install

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

# add to Claude Code
claude mcp add --transport http jdhart81-agent-arbitration 'https://mcp.viridisconservation.com/arbitration/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "jdhart81-agent-arbitration": {
      "url": "https://mcp.viridisconservation.com/arbitration/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jdhart81-agent-arbitration": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/arbitration/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.jdhart81-agent-arbitration]
url = "https://mcp.viridisconservation.com/arbitration/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jdhart81-agent-arbitration": {
      "type": "remote",
      "url": "https://mcp.viridisconservation.com/arbitration/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jdhart81-agent-arbitration --url 'https://mcp.viridisconservation.com/arbitration/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  jdhart81-agent-arbitration:
    url: "https://mcp.viridisconservation.com/arbitration/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jdhart81-agent-arbitration": {
      "Transport": "http",
      "Url": "https://mcp.viridisconservation.com/arbitration/mcp"
    }
  }
}
# add to Vellum
assistant mcp add jdhart81-agent-arbitration -t streamable-http -u 'https://mcp.viridisconservation.com/arbitration/mcp'
// mcp.json
{
  "mcpServers": {
    "jdhart81-agent-arbitration": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/arbitration/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 +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
  • 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/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
MCP tools · 8 exposed · ~359 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
describe_agent ~13

Fleet-standard self-description.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

file_case ~67

File a dispute over an escrow. Opens the evidence window. Parties must be distinct; amount is in minor currency units (cents).

NameTypeReqDescription
amount_minorintegeryes–
claimantstringyes–
escrow_idstringyes–
respondentstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_case ~26

Fetch the full case record, including any ruling.

NameTypeReqDescription
case_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_cases ~32

List cases, optionally filtered by state (FILED|EVIDENCE_OPEN|RULED).

NameTypeReqDescription
state–––
NameTypeReqDescription
resultstringyes–

No examples provided.

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.

NameTypeReqDescription
case_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

set_trust_scores ~43

Attach trust-oracle reputation scores (party -> [0,1]) as ruling inputs.

NameTypeReqDescription
case_idstringyes–
scoresobjectyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

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.

NameTypeReqDescription
case_idstringyes–
contentstring––
kindstringyes–
partystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_ruling ~43

Recompute the ruling from its cited evidence + trust inputs and check it matches the stored allocation (machine-checkable justice).

NameTypeReqDescription
case_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

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 359 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.