Hive Dispute
Server Details
Agent-to-agent dispute resolution and arbitration with on-chain settlement
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2024-11-05
- URL
- Repository
- srotzin/hive-mcp-dispute
- GitHub Stars
- 0
- Server Listing
- hive-mcp-dispute
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool addresses a distinct aspect: checking a specific counterparty's history, listing providers, getting a recommendation, and a daily summary. There is no overlap in purpose, and the descriptions clearly differentiate them.
All tools share the 'dispute_' prefix and use clear, descriptive suffixes (check, providers, route, today). The naming follows a predictable and consistent pattern, making the tool set easy to navigate.
With 4 tools, the server is well-scoped for its purpose of surfacing dispute information and routing options. Each tool earns its place and there are no redundant or excessive entries.
The set covers the full lifecycle for the server's stated role: checking dispute history, listing providers, routing to a provider, and providing a daily summary. Since the server explicitly does not file or enforce, there are no missing operations that would cause dead ends.
Available Tools
4 toolsdispute_checkAInspect
Given a counterparty address + chain, return public dispute history, active arbitration cases, and on-chain reversal-pattern flags. Sources: Kleros / UMA / Reality.eth subgraphs (with direct on-chain RPC fallback) plus Etherscan-family transaction scans. Observational only — Hive does NOT judge, freeze, or enforce.
Inputs: chain (required), address (required).
dispute_providersAInspect
List available third-party arbitration protocols (Kleros, UMA Optimistic Oracle, Reality.eth) with current case load, intake URLs, and jurisdiction model. Hive is not one of them — Hive only surfaces signal.
Inputs: no named parameters.
dispute_routeAInspect
Given a case description, disputed amount in USD, and optional jurisdiction preference, return ranked arbitration provider options. NO automatic filing — Hive returns options + intake URLs only. The disputing party files directly with the chosen provider.
Inputs: amount_usd (required), description (required), jurisdiction.
dispute_todayBInspect
24-hour rollup: flagged-counterparty count + top arbitration providers by active case load.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Governance framework, dispute resolution, and arbitration for agents
Agent liability insurance — claims, premiums, and on-chain payouts
Multi-agent settlement and clearing with validator consensus
Deterministic, machine-verifiable dispute resolution for A2A escrows.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables autonomous AI agents to submit principal-bounded sealed offers for commercial or SLA disputes, settle overlapping offers deterministically at a midpoint or fair split, and receive verifiable signed settlement instructions or UNRESOLVED certificates while keeping confidential terms private.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMulti-party escrow and settlement for autonomous agent transactions with x402 micropayments and dispute resolution on Base, Ethereum, or Solana.MIT

Synpareia Trust Toolkitofficial
AlicenseAqualityCmaintenanceVerifiable dealings with other agents: prove what you did, vet who you deal with, bind agreements3663 PyPIApache 2.0- AlicenseNot gradedqualityBmaintenanceNon-custodial 2-of-3 Bitcoin escrow for AI agents. Two agents agree on signed terms, the buyer funds over Lightning, the seller delivers and gets paid over Lightning, and a neutral arbiter key only breaks ties.418 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.