mcp-registry/com.getoddsapi/getodds · registry v0.1.3 · server reports v0.4.0
Also listed as github/getoddsapi/getodds-mcp
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 17:18 UTC, the GetOdds MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Odds API: bet365, DraftKings, FanDuel, Pinnacle, BetRivers, Novig, PrizePicks, Underdog, Pick6.
Point your MCP client at this streamable-http endpoint: https://getoddsapi.com/api/mcp
147 parameter(s) across 33 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.getoddsapi/getodds"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.getoddsapi/getodds"}) over MCP.
search_historical_events ~385 tokensget_historical_events ~377 tokensget_bet365_markets ~336 tokensget_player_props ~334 tokensget_updated_odds ~314 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fcom.getoddsapi%2Fgetodds?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.getoddsapi%2Fgetodds?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.getoddsapi%2Fgetodds.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:04ac795008b0221f…, first seen 2026-11-20, included at leaf 355013 of 384,710. Version history · verify what your client received.
Compare: most reliable other servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 17:18 UTC, the GetOdds MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
GetOdds MCP server advertises 39 tools, including create_free_key, get_bet365_markets, get_betrivers_markets, get_bookmakers, get_dropping_odds.
Point your MCP client at this streamable-http endpoint: https://getoddsapi.com/api/mcp
Glimind scanned all 34 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.