About Hive Dispute
Hive Dispute is an MCP server that gives agents observational signals about counterparties and arbitration activity before payment. It reports public-source dispute and reversal data, but does not arbitrate, file cases, hold funds, or enforce outcomes.
Key features
- 01Check counterparty dispute and reversal signals
- 02List arbitration providers and case loads
- 03Rank provider options from case details
- 04Show 24-hour flagged-counterparty totals
Use cases
- 01Review a counterparty before agreeing to payment
- 02Check current activity at arbitration providers
- 03Compare possible dispute-resolution providers
- 04Monitor recent flagged-counterparty signals
MCP support
Exposes dispute checks, provider information, routing suggestions, and daily signal summaries to MCP clients over Streamable HTTP. The server supplies observational data only and does not resolve or enforce disputes.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://hive-mcp-gateway.onrender.com/dispute/mcpclaude mcp add --transport http srotzin-hive-mcp-dispute https://hive-mcp-gateway.onrender.com/dispute/mcp{"mcpServers":{"srotzin-hive-mcp-dispute":{"type":"http","url":"https://hive-mcp-gateway.onrender.com/dispute/mcp"}}}Open in Cursor{"servers":{"srotzin-hive-mcp-dispute":{"type":"http","url":"https://hive-mcp-gateway.onrender.com/dispute/mcp"}}}Open in VS Code{"mcpServers":{"srotzin-hive-mcp-dispute":{"type":"http","url":"https://hive-mcp-gateway.onrender.com/dispute/mcp"}}}{"mcpServers":{"srotzin-hive-mcp-dispute":{"serverUrl":"https://hive-mcp-gateway.onrender.com/dispute/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
4| Parameter | Type | Required | Description |
|---|---|---|---|
| chain | string | Yes | ethereum | base | arbitrum |
| address | string | Yes | 0x-prefixed counterparty address (20 bytes) |
Details
From the project READMEhive-mcp-dispute
Observational dispute/chargeback signal surface for agent-to-agent commerce.
Hive does NOT arbitrate, judge, freeze funds, or enforce dispute outcomes. This is observational signal data only. Disputes are resolved by third-party protocols (Kleros, UMA, Reality.eth) or off-chain legal process. Hive is not a court.
What this is
An MCP server that surfaces arbitration and reversal signals an agent can read before it agrees to a counterparty payment. It pulls from real public sources:
| Source | Surface | Method |
|---|---|---|
| Kleros court-v2 subgraph | Active disputes, recent rulings | GraphQL (with on-chain eth_getLogs fallback against KlerosLiquid 0x988b…28069) |
| UMA Optimistic Oracle v3 subgraph | Open assertions, disputed assertions | GraphQL (with on-chain fallback against 0xfb55…C0dE) |
| Reality.eth subgraph | Open questions, pending arbitration | GraphQL (with on-chain fallback against 0xAf33…49CA) |
| Etherscan / Basescan / Arbiscan | On-chain reversal-pattern detection (paired out-then-in within 24h, value within 5%, same peer) | REST account/txlist |
What this is NOT
- ❌ A court
- ❌ An arbitrator
- ❌ A custodian of disputed funds
- ❌ A filing agent (no auto-filing with Kleros / UMA / Reality.eth)
- ❌ An enforcement layer
Tools
| Tool | Description |
|---|---|
dispute_check | Given counterparty address + chain → dispute history + active arbitration cases + on-chain reversal flags |
dispute_providers | List Kleros / UMA / Reality.eth with current case load + intake URLs |
dispute_route | Given case description + amount + jurisdiction → ranked provider options (no auto-filing) |
dispute_today | 24h flagged-counterparty count + top providers by active case load |
Endpoints (backend)
| Method | Path | Tool |
|---|---|---|
| POST | /v1/dispute/check | dispute_check |
| GET | /v1/dispute/providers | dispute_providers |
| POST | /v1/dispute/route | dispute_route |
| GET | /v1/dispute/today | dispute_today |
Every response carries the observational disclaimer and brand_color: "#C08D23".
Install
Smithery (recommended for MCP clients)
npx -y @smithery/cli install hive-mcp-dispute --client claude
Manual (local dev)
git clone https://github.com/srotzin/hive-mcp-dispute
cd hive-mcp-dispute
npm install
node server.js
The server listens on :3000 by default and exposes:
POST /mcp— JSON-RPC 2.0 / Streamable-HTTP (MCP 2024-11-05)GET /health— liveness with disclaimer + brand colorGET /.well-known/mcp.json— discovery manifest
Configure
| Env var | Default | Purpose |
|---|---|---|
PORT | 3000 | Listen port |
HIVE_BASE | https://hivemorph.onrender.com | Backend root |
Brand
Hive Civilization gold — Pantone 1245 C / #C08D23. Baked into every response.
Disclaimer (canonical, baked into every response)
Hive does not arbitrate, judge, freeze funds, or enforce dispute outcomes. This is observational signal data only. Disputes are resolved by third-party protocols (Kleros, UMA, Reality.eth) or off-chain legal process. Hive is not a court.
License
MIT — see LICENSE.
Hive Civilization Directory
Part of the Hive Civilization — agent-native financial infrastructure.
- Endpoint Directory: https://thehiveryiq.com
- Live Leaderboard: https://hive-a2amev.onrender.com/leaderboard
- Revenue Dashboard: https://hivemine-dashboard.onrender.com
- Other MCP Servers: https://github.com/srotzin?tab=repositories&q=hive-mcp
Brand: #C08D23
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.