SportsAPIs.dev

https://server.smithery.ai/sportsapis/sportsapis/mcp

● healthy

The SportsAPIs.dev MCP server answers questions about our directory of 45+ odds APIs and sports data APIs. It has three read-only tools. find_sports_apis returns a ranked short list for your sport and the features you need, such as live odds, WebSocket, player props or a free tier. compare_sports_apis puts two to four providers side by side. get_sports_api_details returns what our review of one provider records, from pricing to FAQs. The server needs no key and no sign-up, and it runs over Streamable HTTP at https://sportsapis.dev/mcp. It serves no odds, scores or betting picks: it's for developers choosing a data feed. Every answer links to the provider's review page on sportsapis.dev.

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

2025-06-18

negotiated, not declared

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	23/25	Endpoint answers the MCP initialize handshake (5652 ms); very slow response -2.
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	28/28 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 3 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Very slow (5652 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 60% of peers; This listing 83 · peer median 81
Latency: Faster than 17% of peers; This listing 681 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-16 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/sportsapis/sportsapis/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/sportsapis/sportsapis/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://sportsapis.dev/sports-mcp-servers#sportsapis-mcp

Listed at (smithery)

https://sportsapis.dev/sports-mcp-servers#sportsapis-mcp