mcpbeat

Hive Dispute MCP Server

io.github.srotzin/hive-mcp-dispute
answering

Hive Dispute is answering right now. Last checked 9 min ago. It exposes 4 tools. Last commit 2 May 2026.

Agent-to-agent dispute resolution and arbitration with on-chain settlement

Uptime history 43 hours of history · worst hour 0%
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
248 ms
Response time
average over 24h
0
Stars
last commit 2 May 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add hive-mcp-dispute --transport http https://hive-mcp-gateway.onrender.com/dispute/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hive-mcp-dispute": {
      "url": "https://hive-mcp-gateway.onrender.com/dispute/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.hive-mcp-dispute]
url = "https://hive-mcp-gateway.onrender.com/dispute/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "hive-mcp-dispute": {
      "url": "https://hive-mcp-gateway.onrender.com/dispute/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "hive-mcp-dispute": {
      "url": "https://hive-mcp-gateway.onrender.com/dispute/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dispute
dispute_check
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.
dispute_providers
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.
dispute_route
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.
dispute_today
24-hour rollup: flagged-counterparty count + top arbitration providers by active case load.

Endpoints

URLTransportStateLatencyChecked
https://hive-mcp-gateway.onrender.com/dispute/mcp streamable-http answering 214 ms 9 min ago

Hive Dispute — questions

Answers built from our own checks of this server.

What can Hive Dispute do?
It exposes 4 tools, read directly from the server on our last check. Among them: dispute_check, dispute_providers, dispute_route, dispute_today. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Hive Dispute working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 248 ms. The bar chart above shows every period we have measured.
How do I connect Hive Dispute?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Hive Dispute need an API key?
No. Hive Dispute completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Hive Dispute?
It answers our handshake in 248 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Hive Dispute open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.