MCP.Market

disputes.online MCP server

online · 100% uptime
by disputes.online·online.disputes/mcp·v1.2.0

Read prediction disputes and the crowd's odds on real-world events from disputes.online.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed disputes.online yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

disputes.online tools (4)

write = sends, deletes, buys or posts
  • get_disputeFree

    Get one dispute from disputes.online by its id or page URL: the question, how it will be decided, the outcomes, how the stakes are split between them, and the deadlines. Also finds a dispute that has already been settled and returns which outcome won next to how the crowd had bet — use it to check a past prediction.

  • list_categoriesFree

    List the categories disputes on disputes.online are filed under, as a flat tree. Use it to find the category_id for a topic before calling search_disputes.

  • search_disputesFree

    Find disputes on disputes.online that are open to bets, with each outcome's share of the stakes. Search by free text with query (a topic, a person, a team, an asset), filter by language, category, country and creation date, and sort by pool size, number of bets, newest or closing time. This is the tool for finding what people are predicting about something, what the crowd thinks the odds are, and what was opened recently — for yesterday's disputes pass yesterday's date as both created_from and created_to.

  • search_disputes_by_tagsFree

    List open disputes on disputes.online that carry every one of the given tags, spelled exactly. Tags are set by a dispute's author, many disputes have none, and their spelling is arbitrary — to find disputes about a subject, use search_disputes with query instead. Use this only when you already know the exact tag.

Public scan report

scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 427ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How disputes.online compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
397 ms
faster than 37% of 30,031 servers

What its tools let an agent do: 4 read

Install disputes.online in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://disputes.online/mcp
Add to Cursor

What the publisher says

From the disputes.online repository's README, as published. We do not edit it. Read it on GitHub

disputes.online MCP server

A public, read-only Model Context Protocol server for disputes.online. It lets an AI agent find open disputes and read how the stakes on them are split — the crowd's implied odds.

Endpoint: https://disputes.online/mcp (Streamable HTTP, no authentication)

Tools

Every dispute comes with its page URL and, per outcome, the share of stakes (implied_probability) and the payout multiplier. Amounts are in QOT, the platform's internal currency. Lists default to English; pass lang for disputes written in another language.

There are no tools that place bets, create disputes or act for a user.

Connecting

Claude Code:

claude mcp add --transport http disputes-online https://disputes.online/mcp

Any client that takes a JSON config:

{ "mcpServers": { "disputes-online": { "type": "http", "url": "https://disputes.online/mcp" } } }

How it works

The server has no database access. It calls the same public API the site uses (https://disputes.online/openapi.json), so it can only say what the site already publishes. It is stateless: any replica answers any request.

Configuration

GET /health answers ok.

Running locally

APP_PORT=8098 \
DISPUTES_URL=https://disputes.online/disputes \
CATEGORIES_URL=https://disputes.online/category \
HISTORY_URL=https://disputes.online/history \
go run ./cmd

Then point a client, or npx @modelcontextprotocol/inspector, at http://localhost:8098/mcp.

Publishing to the MCP registry

server.json describes this server for the official MCP registry under the name online.disputes/mcp. That namespace belongs to whoever controls disputes.online: the site serves a public key at https://disputes.online/.well-known/mcp-registry-auth, and publishing takes the matching private key, kept outside this repository at ~/.mcp-registry/disputes.online.pem.

brew install mcp-publisher
./publish.sh

Bump version in server.json before publishing again; the registry refuses a version it already has.

Tests

go test ./...

License

MIT

Nothing above is checked by us. What we check is on the safety report.

disputes.online: common questions

Is disputes.online MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the disputes.online safety report
How do I install disputes.online?
It runs remotely at disputes.online. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does disputes.online need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is disputes.online maintained?
The last commit was 30 days ago (2026-10-05). The latest release is v1.2.0.
Is disputes.online up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does disputes.online compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.