Is the Therundown Data MCP server down?

mcp-registry/io.github.therundown/data · v0.4.0

healthy
Last checked 2026-10-24 09:40 UTC · handshake 283ms

As of 2026-10-24 09:40 UTC, the Therundown Data MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 13 minutes.

uptime (30d checks)
99.7%
checks observed
4,541
outages (90d)
6
tools
85

Six Product API tools require authentication; protocol metadata discovery is keyless.

Install Therundown Data MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http therundown-data-mcp-server https://mcp.therundown.io/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "therundown-data-mcp-server": {
      "type": "http",
      "url": "https://mcp.therundown.io/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 4 warning(s) across 85 tool(s); ~40,003 tokens of tool definitions.
Scores higher than 7% of 15,635 MCP servers Glimind has audited.
Its tool list costs an agent ~40,003 tokens per session — more than 99% of servers.
71 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions20
Safety hints100
Token cost23
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (5)

4 tool definition(s) exceed ~1,200 tokens each (largest: capture_live_stream, ~1,455).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~3,050 tokens every session. How to fix →

Tools: capture_live_stream, v2GetEventsBySportAndDate, v2GetClosingBySportAndDate, v2GetOpenersBySportAndDate · saves ~3,050 tokens/session

85 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

133 parameter(s) across 75 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: capture_hedge_stream, capture_live_stream, capture_market_stream, capture_v1_stream, get_main_lines and 70 more

Loading this server's tool list costs an agent ~40,003 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

12 tools share an identical description with another tool on this server.

Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →

Tools: v1GetConferencesBySport, v2GetConferencesBySport, v1GetDatesBySport, v2GetDatesBySportID, v1GetDivisionsBySport and 7 more

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.therundown/data"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.therundown/data"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.therundown%2Fdata.svg)](https://glimind.com/server/mcp-registry%2Fio.github.therundown%2Fdata?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.therundown%2Fdata?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.therundown%2Fdata.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.therundown%2Fdata.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.therundown%2Fdata?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cec0a55d6d29770e…, first seen 2026-10-17, included at leaf 1006 of 58,045. Version history · verify what your client received.

Tools (85)

Compare: most reliable data servers · most reliable knowledge servers · most reliable retrieval servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Therundown Data MCP server down right now?

As of 2026-10-24 09:40 UTC, the Therundown Data MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 13 minutes.

How many tools does Therundown Data MCP server provide?

Therundown Data MCP server advertises 85 tools, including capture_hedge_stream, capture_live_stream, capture_market_stream, capture_v1_stream, get_main_lines.

How do I install Therundown Data MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.therundown.io/mcp

Is the Therundown Data MCP server safe to connect to an AI agent?

Glimind scanned all 85 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Therundown Data MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve