# SportsAPIs.dev (remote · sportsapis.dev)

Find and compare sports odds and data APIs, and read the SportsAPIs.dev review of each one.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `sportsapis.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-sportsapis-sportsapis/sportsapis.md), [page](https://verifymcp.io/servers/dev-sportsapis-sportsapis/sportsapis)

## Channel facts

- Endpoint: `https://sportsapis.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 34/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-sportsapis-sportsapis 'https://sportsapis.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-sportsapis-sportsapis": {
      "url": "https://sportsapis.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-sportsapis-sportsapis": {
      "type": "http",
      "url": "https://sportsapis.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-sportsapis-sportsapis]
url = "https://sportsapis.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-sportsapis-sportsapis": {
      "type": "remote",
      "url": "https://sportsapis.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-sportsapis-sportsapis --url 'https://sportsapis.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-sportsapis-sportsapis:
    url: "https://sportsapis.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-sportsapis-sportsapis": {
      "Transport": "http",
      "Url": "https://sportsapis.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-sportsapis-sportsapis -t streamable-http -u 'https://sportsapis.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-sportsapis-sportsapis": {
      "type": "http",
      "url": "https://sportsapis.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +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.

### 2026-11-02 (score 75, +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.

### 2026-10-31 (score 74, +1)

- [security] 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

### 2026-10-29 (score 73, 0)

- [security] Tool “find_sports_apis” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 233 → 305
- [cosmetic] “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”

### 2026-10-28 (score 73, +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.

### 2026-10-26 (score 72, +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.

### 2026-10-24 (score 71, −4)

- [functional improvement] 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”
- [cosmetic] “find_sports_apis” added an optional parameter “exclude_providers”
- [cosmetic] “find_sports_apis” reworded the description of “sport”

### 2026-10-23 (score 75, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

## MCP tools (3)

### `find_sports_apis` (~958 tokens)

Find sports data and odds APIs

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.

Input parameters:

- `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…

Output parameters:

- `directory_url` (string)
- `filters_applied` (object)
- `next_steps` (array): Which tool to call for the likely follow-up questions.
- `notes` (array)
- `results` (array)
- `total_matches` (integer)

### `compare_sports_apis` (~198 tokens)

Compare sports APIs side by side

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.

Input parameters:

- `providers` (array, required): Two to four provider names as developers write them, for example ["The-Odds-API", "OddsPapi", "SportsGamesOdds"].

Output parameters:

- `differences` (array)
- `next_steps` (array): Which tool to call for the likely follow-up questions.
- `notes` (array)
- `providers` (array)
- `shared_confirmed` (array)

### `get_sports_api_details` (~167 tokens)

Get the SportsAPIs.dev review of one provider

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.

Input parameters:

- `provider` (string, required): Provider name or slug, for example "OddsPapi", "the odds api", "sportsdata-io".

Output parameters:

- `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)
- `name` (string)
- `next_steps` (array): Which tool to call for the likely follow-up questions.
- `pricing_summary` (string)
- `provider_url` (string)
- `review_sections` (array)
- `review_url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-sportsapis-sportsapis/sportsapis#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://sportsapis.dev/mcp
- Website: https://sportsapis.dev/sports-mcp-servers
- Changelog RSS feed: https://verifymcp.io/servers/dev-sportsapis-sportsapis/sportsapis.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-sportsapis-sportsapis/sportsapis/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-sportsapis-sportsapis/sportsapis.json
- HTML version of this page: https://verifymcp.io/servers/dev-sportsapis-sportsapis/sportsapis