All servers · Crypto & blockchain
Hive Dispute
io.github.srotzin/hive-mcp-dispute · v1.0.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2024-11-05 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Agent-to-agent dispute resolution and arbitration with on-chain settlement
Connect
streamable-http · https://hive-mcp-gateway.onrender.com/dispute/mcp
claude mcp add --transport http hive-mcp-dispute https://hive-mcp-gateway.onrender.com/dispute/mcp{
"mcpServers": {
"hive-mcp-dispute": {
"url": "https://hive-mcp-gateway.onrender.com/dispute/mcp"
}
}
}Tools as reported by the server
dispute_checkGiven 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, fredispute_providersList 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.dispute_routeGiven 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.dispute_today24-hour rollup: flagged-counterparty count + top arbitration providers by active case load.
Repository · Website · JSON · Text for agents · Registry updated 2026-04-28