SportsAPIs.dev
REMOTE · SPORTSAPIS.DEV
Find and compare sports odds and data APIs, and read the SportsAPIs.dev review of each one.
Available components
Last scanned (13 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability34
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1595 tokens (~319/item across 5 items; 3 tools + 2 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 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.
- 2 Nov 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.
- 31 Oct 26 +1
- Resource “sportsapis-provider-cards” now points somewhere else: ui://sportsapis/cards-v5.html → ui://sportsapis/cards-v7.html security
- Tool “find_sports_apis” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- Tool “find_sports_apis” rewrote its description, which is the text the model reads security
- Schema quality: 233 → 305 ▼ functional
- “find_sports_apis” added an optional parameter “books” cosmetic
- “find_sports_apis” added an optional parameter “leagues” cosmetic
- “find_sports_apis” added an optional parameter “markets” cosmetic
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −4
- Schema quality: 363 → 233 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 0 functional
- Schema quality: excellent → good functional
- New resource “sportsapis-provider-cards” functional
- New resource “sportsapis-compare-cards” functional
- “find_sports_apis” added an optional parameter “exclude_providers” cosmetic
- “find_sports_apis” reworded the description of “sport” cosmetic
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
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://sportsapis.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sportsapis.dev | CN=YR1,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | RSA 2048 | SHA256-RSA | 65d3c0c468138bfea5759c7737522a51f74 |
| SANs: sportsapis.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sportsapis.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| sportsapis.dev. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sportsapis.dev/mcp | Verified | 200 | |
| http (plaintext) | http://sportsapis.dev/mcp | HTTPS enforced | 308 | https://sportsapis.dev/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 →
compare_sports_apis Compare sports APIs side by side ~198
Use this when a developer names two to four sports odds or sports data API providers and wants them compared, for example "The-Odds-API vs OddsPapi" or "SportsGamesOdds or SportsData.io for player props". Returns a side-by-side table of researched feature support (pregame, live, Bet365, Pinnacle, closing odds, futures, same game parlay, deeplinks, settlement, stats, schedules, WebSocket, MCP server, esports), pricing scale, free tier, sports mentioned in our reviews, the differences between them, and the SportsAPIs.dev review URL for each. Providers must be in the SportsAPIs.dev directory. Do not use this to compare betting odds or sportsbook prices for a game.
| Name | Type | Req | Description |
|---|---|---|---|
| providers | array | yes | Two to four provider names as developers write them, for example ["The-Odds-API", "OddsPapi", "SportsGamesOdds"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| differences | array | yes | – |
| next_steps | array | – | Which tool to call for the likely follow-up questions. |
| notes | array | – | – |
| providers | array | yes | – |
| shared_confirmed | array | – | – |
No examples provided.
find_sports_apis Find sports data and odds APIs ~958
Use this when a developer asks which sports odds API, sports data API, sportsbook odds feed, live odds API, esports odds API, player props API, or free sports API to use for an app, model, or odds comparison tool. Filters the providers researched by SportsAPIs.dev by sport, required features (live odds, WebSocket streaming, Bet365 or Pinnacle odds, historical odds, player props, stats, live scores, MCP server), free tier, price tier and region. Returns a ranked short list with a one-line reason and the SportsAPIs.dev review URL for each provider. Ranking: every feature, free tier, price and region filter must match; sport is a boost, not a filter, because sport lists come from mentions in our reviews. Featured partners of SportsAPIs.dev rank first and are labelled as featured partners. Within each group, providers whose review names the sport come first; with a free tier or price tier filter, cheaper paid plans come next. Other ties follow a daily rotation, so no provider is always first. Features the user did not ask for do not change the order. With no sport, feature, book, league, market, budget or region at all, it returns no providers and asks what the user needs. Optional books, leagues and markets filters (for example "DraftKings", "NBA", "player points") keep only providers in the SportsAPIs.dev Coverage Map that carry every requested value, so use them only when the user needs a specific book, league or market confirmed. Do not use this for betting picks, game predictions, or the odds of a specific match; it has no odds data, only facts about API providers.
| Name | Type | Req | Description |
|---|---|---|---|
| books | array | – | Sportsbooks, exchanges or prediction markets the API must carry odds from, as canonical ids or display names, case-insensitive, for example "DraftKings", "bet365" or "Kalshi". Every value must be car… |
| exclude_providers | array | – | Provider names already shown in this chat. Use it when the user asks for more or other options: these providers are skipped, so the result and the cards show new ones. |
| free_tier | boolean | – | true = only providers with a confirmed free tier or free plan. |
| kind | string | – | "odds" for odds and betting-market APIs, "data" for scores, stats and schedules APIs with no odds. Default "any". |
| leagues | array | – | Leagues the API must carry odds for, as canonical ids or display names, case-insensitive, for example "NBA", "EPL" or "Premier League". Every value must be carried for a provider to match. Only provi… |
| limit | integer | – | How many providers to return. Default 5. |
| markets | array | – | Bet markets the API must carry, as canonical ids or display names, case-insensitive, for example "player points", "spreads" or "anytime touchdown". Every value must be carried for a provider to match… |
| max_price_tier | integer | – | Highest acceptable entry price tier on a 1 to 5 scale (1 = about $20/mo, 5 = $1000+/mo). Example: 2 keeps providers whose cheapest paid plan is tier 2 or lower. |
| needs | array | – | Features the API must have. Every listed need must be confirmed for a provider to appear. |
| region | string | – | Bookmaker focus: "usa" for US sportsbooks and Bookmaker.eu feeds, "international" for European and Asian books including Pinnacle feeds. Default "any". |
| sport | string | – | Sport or league the developer needs, for example "NFL", "soccer", "tennis", "esports", "college football", or "prediction markets" for Kalshi, Polymarket and similar venues. Boosts providers whose re… |
| Name | Type | Req | Description |
|---|---|---|---|
| directory_url | string | yes | – |
| filters_applied | object | – | – |
| next_steps | array | – | Which tool to call for the likely follow-up questions. |
| notes | array | – | – |
| results | array | yes | – |
| total_matches | integer | yes | – |
No examples provided.
get_sports_api_details Get the SportsAPIs.dev review of one provider ~167
Use this when a developer asks about one specific sports odds or sports data API by name, for example "Is The-Odds-API free?", "Does OddsPapi have a WebSocket?", "OddsJam API pricing", or "Sportradar API review". Returns everything the SportsAPIs.dev review page records: feature support, pricing tiers from our review, free tier, sports mentioned, strengths, the full review text, FAQs, alternatives in the directory, and the review URL. The provider must be in the SportsAPIs.dev directory. Do not use this for a sportsbook, a league, or a betting question.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Provider name or slug, for example "OddsPapi", "the odds api", "sportsdata-io". |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | – |
| coverage | object|null | – | What the SportsAPIs.dev Coverage Map records for this provider, with the date we checked it. Null when the provider is not in the map. |
| faqs | array | – | – |
| features | object | yes | – |
| name | string | yes | – |
| next_steps | array | – | Which tool to call for the likely follow-up questions. |
| pricing_summary | string | – | – |
| provider_url | string | yes | – |
| review_sections | array | – | – |
| review_url | string | yes | – |
No examples provided.
How do I install the SportsAPIs.dev MCP server?
SportsAPIs.dev is a hosted endpoint at https://sportsapis.dev/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 · sportsapis.dev
claude mcp add --transport http dev-sportsapis-sportsapis 'https://sportsapis.dev/mcp'
What is the SportsAPIs.dev MCP server?
SportsAPIs.dev is an MCP server listed in the public MCP registry as dev.sportsapis/sportsapis. Find and compare sports odds and data APIs, and read the SportsAPIs.dev review of each one. This page covers its hosted endpoint (https://sportsapis.dev/mcp).
Is the SportsAPIs.dev MCP server safe to use?
SportsAPIs.dev scores 76 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 SportsAPIs.dev MCP server expose?
SportsAPIs.dev exposes 3 tools: find_sports_apis, compare_sports_apis, get_sports_api_details. Their descriptions and schemas cost roughly 1,323 tokens of context every time the server is loaded.
Does the SportsAPIs.dev MCP server require authentication?
No. We connected to SportsAPIs.dev without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SportsAPIs.dev MCP server still maintained?
SportsAPIs.dev 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.
What did VerifyMCP test on the SportsAPIs.dev MCP server?
VerifyMCP ran 14 checks on SportsAPIs.dev, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.