Sports Odds API
Related Servers
Alternatives to Sports Odds API
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables fetching sportsbook odds, live scores, and event information across 70+ books and 30+ leagues, with tools to list sports, get scores, and discover events.430 npm1MIT
- FlicenseNot gradedqualityDmaintenanceProvides comprehensive sports intelligence including live scores, standings, schedules, betting odds, news, highlights, and more via SSE transport.-

sportapi-mcpofficial
AlicenseAqualityBmaintenanceLive and prematch sports odds, scores, live statistics and match search from SportAPI (football, basketball, tennis, esports and more). Works with demo data without an API key.111MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to fetch live football odds and team form, and flag matches where the market price diverges from a simple form-based estimate.Eclipse Public 2.0
- AlicenseAqualityBmaintenanceEnables MCP-compatible clients to access sports betting odds, player props, prediction markets, live previews, coverage checks, and ParlayAPI account signup through native tools.2250 PyPI1MIT

Odds-API MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to access sports betting odds data from 265+ bookmakers across 34 sports, including events, odds, historical data, arbitrage, and value bets.25160 npm2MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its stated scope (current Kambi-book odds comparison, not DraftKings/FanDuel or historical data) is explicitly bounded, leaving no internal overlap to confuse an agent.
The name 'publicrecords--sports-odds-api' is a namespaced actor slug rather than a verb_noun action, which is readable but not a predictable tool convention. With a single tool there is no pattern to be consistent with, so it lands as mixed-but-legible.
A single tool is thin for a data-fetching server, but here it is a deliberate one-tool proxy for a whole Apify actor, so the scope isn't mismatched so much as shallow. It sits at the borderline of 'one tool feels thin.'
The core operation—get odds rows plus run/dataset IDs—is covered, but the description advertises paging the full dataset while exposing no tool to fetch subsequent pages or list supported sportsbooks/leagues/markets. Agents can get the first page but hit a dead end for anything beyond it.