# disputes.online (remote · disputes.online)

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

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `disputes.online`: 83/100 (this document), [markdown](https://verifymcp.io/servers/online-disputes-mcp/disputes.md), [page](https://verifymcp.io/servers/online-disputes-mcp/disputes)

## Channel facts

- Endpoint: `https://disputes.online/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1188 tokens (~297/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the disputes.online MCP server?

disputes.online is a hosted endpoint at https://disputes.online/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "online-disputes-mcp": {
      "url": "https://disputes.online/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "online-disputes-mcp": {
      "type": "http",
      "url": "https://disputes.online/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.online-disputes-mcp]
url = "https://disputes.online/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "online-disputes-mcp": {
      "type": "remote",
      "url": "https://disputes.online/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add online-disputes-mcp --url 'https://disputes.online/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  online-disputes-mcp:
    url: "https://disputes.online/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "online-disputes-mcp": {
      "Transport": "http",
      "Url": "https://disputes.online/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add online-disputes-mcp -t streamable-http -u 'https://disputes.online/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, 0)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `get_dispute` (~99 tokens)

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.

Input parameters:

- `dispute` (string, required): the dispute's id (UUID) or the URL of its page on disputes.online

Output parameters:

- `betting_closes` (string): when betting closes, RFC 3339 UTC; absent for a settled dispute
- `category` (string): category name
- `category_id` (integer): category id
- `country` (string): ISO 3166-1 alpha-2 country the dispute is about
- `created` (string): when the dispute was created, RFC 3339 UTC; absent for a settled dispute
- `dates_estimated` (boolean): true when the event has no fixed date and the two dates are estimates
- `description` (string): the full text, including how the result will be decided
- `id` (string): dispute id (UUID)
- `language` (string): language code, or all; absent for a settled dispute
- `outcomes` (null|array): the possible results and how the stakes are split between them — for a settled dispute, how they were split when it was decided
- `result_due` (string): when the result is due, RFC 3339 UTC; absent for a settled dispute
- `settled_at` (string): when the dispute was decided, RFC 3339 UTC; present only for a settled dispute
- `status` (string): new: no bets yet; in_process, hot, very_hot: accepting bets, by popularity; ready: betting closed, awaiting the result; done or dispute: decided but still being paid out or contested; settled: decide…
- `tags` (null|array): lowercase tags
- `title` (string): the question, taken from the first line of the description
- `total_bets` (integer): number of bets placed
- `total_staked_qot` (number): pool size in QOT, the platform's internal currency — not dollars
- `url` (string): the dispute's page on disputes.online; link this when citing
- `winning_outcome` (string): name of the outcome that won; present only for a settled dispute that had a winner

### `list_categories` (~41 tokens)

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.

Output parameters:

- `categories` (null|array): every category, as a flat list

### `search_disputes` (~458 tokens)

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.

Input parameters:

- `category_id` (integer): only disputes in this category or any category below it; ids come from list_categories
- `country` (string): ISO 3166-1 alpha-2 code of the country the dispute is about, for example US
- `created_from` (string): only disputes created at or after this moment, UTC. Either a day, 2026-10-07 (from the start of that day), or a full timestamp, 2026-10-07T12:00:00Z.
- `created_to` (string): only disputes created at or before this moment, UTC. Either a day, 2026-10-07 (through the end of that day), or a full timestamp. For one day's disputes pass the same day as created_from and created_…
- `lang` (string): two-letter language code of the disputes to return: en, ua (Ukrainian), pl, de and so on. Defaults to en. Disputes marked all are always included.
- `limit` (integer): page size, 1 to 20; defaults to 10
- `offset` (integer): number of disputes to skip, for paging
- `query` (string): free text to look for, for example bitcoin or trump impeachment. A dispute matches when every word occurs in its text or among its tags; fewer words find more. Leave empty to list everything.
- `sort` (string): amount (largest pool first; the default), bets (most bets first), newest (most recently created first), closing_soon (betting closes soonest first), result_soon (result due soonest first)

Output parameters:

- `disputes` (null|array): this page of disputes
- `offset` (integer): how many disputes were skipped before this page
- `total` (integer): number of disputes matching the request across all pages

### `search_disputes_by_tags` (~172 tokens)

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.

Input parameters:

- `lang` (string): two-letter language code of the disputes to return; defaults to en
- `limit` (integer): page size, 1 to 20; defaults to 10
- `offset` (integer): number of disputes to skip, for paging
- `tags` (null|array, required): one or more tags; a dispute matches only if it carries every one of them, spelled exactly. Tags are single lowercase words, for example politics or usa.

Output parameters:

- `disputes` (null|array): this page of disputes
- `offset` (integer): how many disputes were skipped before this page
- `total` (integer): number of disputes matching the request across all pages

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/online-disputes-mcp/disputes#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-09: 71
- 2026-10-06: 70

## Common questions

### What is the disputes.online MCP server?

disputes.online is an MCP server listed in the public MCP registry as online.disputes/mcp. Read prediction disputes and the crowd's odds on real-world events from disputes.online. This page covers its hosted endpoint (https://disputes.online/mcp).

### Is the disputes.online MCP server safe to use?

disputes.online scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the disputes.online MCP server expose?

disputes.online exposes 4 tools: get_dispute, list_categories, search_disputes, search_disputes_by_tags. Their descriptions and schemas cost roughly 770 tokens of context every time the server is loaded.

### Does the disputes.online MCP server require authentication?

No. We connected to disputes.online without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the disputes.online MCP server still maintained?

disputes.online is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the disputes.online MCP server?

VerifyMCP ran 13 checks on disputes.online, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://disputes.online/mcp
- Repository: https://github.com/peccancy/mcp
- Website: https://disputes.online/developers
- Changelog RSS feed: https://verifymcp.io/servers/online-disputes-mcp/disputes.xml
- Changelog JSON feed: https://verifymcp.io/servers/online-disputes-mcp/disputes/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/online-disputes-mcp/disputes.json
- HTML version of this page: https://verifymcp.io/servers/online-disputes-mcp/disputes