TheRundown Data MCP
REMOTE · MCP.THERUNDOWN.IO · SCANNED SEP 23
Six Product API tools require authentication; protocol metadata discovery is keyless.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1286 tokens (~183/item across 7 items; 6 tools + 1 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the TheRundown Data MCP server?
TheRundown Data MCP is a hosted endpoint at https://mcp.therundown.io/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 · mcp.therundown.io
claude mcp add --transport http therundown-data 'https://mcp.therundown.io/mcp'
{
"mcpServers": {
"therundown-data": {
"url": "https://mcp.therundown.io/mcp"
}
}
} {
"servers": {
"therundown-data": {
"type": "http",
"url": "https://mcp.therundown.io/mcp"
}
}
} [mcp_servers.therundown-data] url = "https://mcp.therundown.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"therundown-data": {
"type": "remote",
"url": "https://mcp.therundown.io/mcp",
"enabled": true
}
}
} openclaw mcp add therundown-data --url 'https://mcp.therundown.io/mcp' --transport streamable-http
mcp_servers:
therundown-data:
url: "https://mcp.therundown.io/mcp" {
"McpServers": {
"therundown-data": {
"Transport": "http",
"Url": "https://mcp.therundown.io/mcp"
}
}
} assistant mcp add therundown-data -t streamable-http -u 'https://mcp.therundown.io/mcp'
{
"mcpServers": {
"therundown-data": {
"type": "http",
"url": "https://mcp.therundown.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 42 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 10 Sept 26 33
First indexed and scored.
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 23 Sept 2026 · Probed https://mcp.therundown.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.therundown.io | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 9 Sept 2026 | 25 Mar 2027 | RSA 2048 | SHA256-RSA | 9e3479947c67ca6fecea8268471017d |
| SANs: mcp.therundown.io | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.therundown.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| therundown.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.therundown.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.therundown.io/mcp | HTTPS enforced |
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_main_lines Get main lines ~168
Fetch open per-affiliate main lines for one event_id. Do not call until list_events returned that exact ID, and do not treat retrieved_at as price freshness. Preserves participant identity, line value and price updated_at. Request live markets 41/42/43 explicitly; each local page is metered.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_ids | array | – | Canonical affiliate IDs; defaults to 19 and 23. Discover current IDs with list_affiliates. |
| event_id | string | yes | Exact event_id from list_events; never a URL. |
| limit | integer | – | – |
| market_ids | array | – | Canonical market IDs. Prematch 1/2/3; live 41/42/43. Discover with list_markets. |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| empty | object | – | – |
| error | string | – | – |
| event_id | string | – | – |
| limit_reason | string|null | – | – |
| message | string | – | – |
| missing_entitlement | string|null | – | – |
| monthly_remaining_points | – | – | – |
| plan | string|null | – | – |
| remaining_points | – | – | – |
| required_plan | string|null | – | – |
| retrieved_at | string | – | – |
| retry_after | – | – | – |
| source_url | string | – | – |
| status | integer | – | – |
| usage | object | – | – |
No examples provided.
list_affiliates List affiliates ~43
List currently published affiliate IDs and names, excluding retired affiliates. Do not use a catalog row as proof of plan access or an open offer for a sport or market.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| empty | object | – | – |
| error | string | – | – |
| event_id | string | – | – |
| limit_reason | string|null | – | – |
| message | string | – | – |
| missing_entitlement | string|null | – | – |
| monthly_remaining_points | – | – | – |
| plan | string|null | – | – |
| remaining_points | – | – | – |
| required_plan | string|null | – | – |
| retrieved_at | string | – | – |
| retry_after | – | – | – |
| source_url | string | – | – |
| status | integer | – | – |
| usage | object | – | – |
No examples provided.
list_events List events ~197
Find event IDs and summaries for one sport and date. Do not use this tool for futures or as a price quote; use the returned exact event ID with get_main_lines. Defaults to open main lines for prematch markets 1/2/3 and affiliates 19/23. Each local page refetches a metered snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_ids | array | – | Canonical affiliate IDs; defaults to 19 and 23. Discover current IDs with list_affiliates. |
| date | string | yes | Calendar date. Without offset, the day starts at midnight UTC. |
| limit | integer | – | – |
| market_ids | array | – | Canonical market IDs. Prematch 1/2/3; live 41/42/43. Discover with list_markets. |
| offset | integer | – | Date-boundary offset in minutes; default UTC. |
| page | integer | – | – |
| sport_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| empty | object | – | – |
| error | string | – | – |
| event_id | string | – | – |
| limit_reason | string|null | – | – |
| message | string | – | – |
| missing_entitlement | string|null | – | – |
| monthly_remaining_points | – | – | – |
| plan | string|null | – | – |
| remaining_points | – | – | – |
| required_plan | string|null | – | – |
| retrieved_at | string | – | – |
| retry_after | – | – | – |
| source_url | string | – | – |
| status | integer | – | – |
| usage | object | – | – |
No examples provided.
list_futures List futures ~136
Read one sport's scoped futures competition page. Do not use this for dated event discovery or treat a partial page as a complete listing. Futures require an eligible Ultra plan or higher and use opaque cursor pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| affiliate_ids | array | – | Canonical affiliate IDs; defaults to 19 and 23. Discover current IDs with list_affiliates. |
| cursor | string | – | – |
| include_settled | boolean | – | – |
| limit | integer | – | – |
| market_ids | array | – | Canonical futures market IDs; defaults to 1141. Discover with list_markets. |
| sport_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| empty | object | – | – |
| error | string | – | – |
| event_id | string | – | – |
| limit_reason | string|null | – | – |
| message | string | – | – |
| missing_entitlement | string|null | – | – |
| monthly_remaining_points | – | – | – |
| plan | string|null | – | – |
| remaining_points | – | – | – |
| required_plan | string|null | – | – |
| retrieved_at | string | – | – |
| retry_after | – | – | – |
| source_url | string | – | – |
| status | integer | – | – |
| usage | object | – | – |
No examples provided.
list_markets List markets ~101
Discover market definitions, or available markets for one sport and date. Do not use definitions as price quotes or combine live with date-based discovery. Catalog sport/live filters use catalog metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| limit | integer | – | – |
| live | boolean | – | – |
| offset | integer | – | Date-boundary offset in minutes; used only with date-based discovery. |
| page | integer | – | – |
| sport_id | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| empty | object | – | – |
| error | string | – | – |
| event_id | string | – | – |
| limit_reason | string|null | – | – |
| message | string | – | – |
| missing_entitlement | string|null | – | – |
| monthly_remaining_points | – | – | – |
| plan | string|null | – | – |
| remaining_points | – | – | – |
| required_plan | string|null | – | – |
| retrieved_at | string | – | – |
| retry_after | – | – | – |
| source_url | string | – | – |
| status | integer | – | – |
| usage | object | – | – |
No examples provided.
list_sports List sports ~35
List current canonical sport IDs and names. Do not use a catalog row as evidence of current events, prices, or plan access.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| empty | object | – | – |
| error | string | – | – |
| event_id | string | – | – |
| limit_reason | string|null | – | – |
| message | string | – | – |
| missing_entitlement | string|null | – | – |
| monthly_remaining_points | – | – | – |
| plan | string|null | – | – |
| remaining_points | – | – | – |
| required_plan | string|null | – | – |
| retrieved_at | string | – | – |
| retry_after | – | – | – |
| source_url | string | – | – |
| status | integer | – | – |
| usage | object | – | – |
No examples provided.
What is the TheRundown Data MCP server?
TheRundown Data MCP is listed in the public MCP registry as io.github.TheRundown/data. Six Product API tools require authentication; protocol metadata discovery is keyless. This page covers its hosted endpoint (https://mcp.therundown.io/mcp).
Is the TheRundown Data MCP server safe to use?
TheRundown Data MCP scores 79 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 TheRundown Data MCP server expose?
TheRundown Data MCP exposes 6 tools: list_sports, list_affiliates, list_markets, list_events, get_main_lines, list_futures. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.
Does the TheRundown Data MCP server require authentication?
Yes. TheRundown Data MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the TheRundown Data MCP server still maintained?
TheRundown Data MCP is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.