Home / MCP registry index / io.github.TheRundown/data

TheRundown Data MCP

io.github.TheRundown/data in the official MCP registry. Endpoint https://mcp.therundown.io/mcp. Source: github.com/TheRundown/data-mcp.

The registry describes it as: Six Product API tools require authentication; protocol metadata discovery is keyless.

We read its 85 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "data": {
      "url": "https://mcp.therundown.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"data","type":"http","url":"https://mcp.therundown.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_sports list_affiliates list_markets list_events get_main_lines list_futures v2GetDelta v2GetAllStats v2GetStatsSample v2GetStatsByEvent v2GetPlayerStatsByEvent v2GetAllMarkets v2GetMarketsDelta v2GetMarketLinePriceHistory v2GetMarketsParticipants v2GetTeamByID v2GetPlayersByTeam v2GetTeamStats v2GetPlayerStatsByTeam v2GetPlayerByID v2GetSports v2GetDatesBySportIDs v2GetMarketsByDate v2GetEventsByDate v2GetTeamsBySport v2GetEventsBySportAndDate v2GetDatesBySportID v2GetDivisionsBySport v2GetConferencesBySport v2GetFuturesForSport v2GetFuturesEventByID v2GetOpenersBySportAndDate v2GetClosingBySportAndDate v2GetMarketsBySportAndDate v2GetBestOddsBySportAndDate v2GetSteamersBySportAndDate v2GetOutliersBySportAndDate v2GetAffiliates v2GetSportsbooks v2GetSeasonTypes v2GetPublicTournament v2GetEventByID v2GetEventOpeners v2GetEventClosing v2GetAvailableMarketsByEvent v2GetMarketHistoryByEvent v2GetOpeningPricesByEvent v2GetMarketLineHistoryByEvent v2GetBestLineByEvent v2GetBestOddsByEvent v2GetPlaysByEvent v2GetHedgeOpportunities v2GetTopHedgeOpportunities v2GetHedgeOpportunityByID v2GetHedgeOpportunitiesByEvent v2GetBestOdds v2GetSteamers v2GetOutliers v2GetParlayBook v2GetBestParlayBook and 25 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-therundown-data/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-therundown-data)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.