disputes.online
REMOTE · DISPUTES.ONLINE
Read prediction disputes and the crowd's odds on real-world events from disputes.online.
Available components
Last scanned (9 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://disputes.online/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=disputes.online | CN=YE2,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 651ca6cd8ce5651c7cad8730af5e765aba0 |
| SANs: *.disputes.online, disputes.online | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of disputes.online. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| online. | present | 30961 | 13 | Verified |
| disputes.online. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://disputes.online/mcp | Verified | 200 | |
| http (plaintext) | http://disputes.online/mcp | HTTPS enforced | 301 | https://disputes.online/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_dispute ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dispute | string | yes | the dispute's id (UUID) or the URL of its page on disputes.online |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | true when the event has no fixed date and the two dates are estimates |
| description | string | yes | the full text, including how the result will be decided |
| id | string | yes | dispute id (UUID) |
| language | string | – | language code, or all; absent for a settled dispute |
| outcomes | null|array | yes | 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 | yes | 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 | yes | lowercase tags |
| title | string | yes | the question, taken from the first line of the description |
| total_bets | integer | yes | number of bets placed |
| total_staked_qot | number | yes | pool size in QOT, the platform's internal currency — not dollars |
| url | string | yes | 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 |
No examples provided.
list_categories ~41
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | null|array | yes | every category, as a flat list |
No examples provided.
search_disputes ~458
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| disputes | null|array | yes | this page of disputes |
| offset | integer | yes | how many disputes were skipped before this page |
| total | integer | yes | number of disputes matching the request across all pages |
No examples provided.
search_disputes_by_tags ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| disputes | null|array | yes | this page of disputes |
| offset | integer | yes | how many disputes were skipped before this page |
| total | integer | yes | number of disputes matching the request across all pages |
No examples provided.
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.
remote · disputes.online
claude mcp add --transport http online-disputes-mcp 'https://disputes.online/mcp'
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.