Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
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

A4/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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 tools
dispute_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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Non-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 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.