Hive Dispute

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

Should I use this

Quality & Safety

B
Description quality
93%
Schema completeness
65%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'dispute_route' description lacks action verbin dispute_route

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~394Tokens (tool definitions)
~482 BTypical response size
Minimal attention impact (0.31% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "hive-mcp-dispute": {
      "url": "https://hive-mcp-gateway.onrender.com/dispute/mcp"
    }
  }
}

Remote endpoints

https://hive-mcp-gateway.onrender.com/dispute/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢dispute_check(address, chain)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "0x-prefixed counterparty address (20 bytes)"
    },
    "chain": {
      "type": "string",
      "description": "ethereum | base | arbitrum"
    }
  },
  "required": [
    "address",
    "chain"
  ]
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {}
}
⚪dispute_route(description, amount_usd, jurisdiction)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "description": {
      "type": "string",
      "description": "Free-form case description (max 2000 chars)"
    },
    "amount_usd": {
      "type": "number",
      "description": "Disputed amount in USD"
    },
    "jurisdiction": {
      "type": "string",
      "description": "Optional preference (e.g. 'decentralized', 'optimistic', 'crowdsourced')"
    }
  },
  "required": [
    "description",
    "amount_usd"
  ]
}
🟢dispute_today

24-hour rollup: flagged-counterparty count + top arbitration providers by active case load.

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools
verifiedversion not recorded4 tools