Odds De-vig MCP Server
Related Servers
Alternatives to Odds De-vig MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables sports betting analytics and actuarial mathematics through tools that de-vig 3-way odds into unbiased probabilities and compute bivariate Poisson/Dixon-Coles scoreline probabilities locally, with no external API calls.MIT
- AlicenseAqualityBmaintenanceProvides tools for live sportsbook odds, player props, scores, football xG, historical closing lines, US horse racing entries and results, and prediction-market prices through a hosted endpoint and local stdio proxy.81MIT
- AlicenseNot gradedqualityCmaintenanceWraps the Sports Game Odds API to provide sports game odds data through natural language queries.284 npm1MIT
- 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.297 npm1MIT
- AlicenseNot gradedqualityCmaintenanceSorqen is a sports fair-value API + MCP server: it turns sportsbook odds into a versioned, no-vig consensus probability for NFL/NBA/MLB/NHL moneyline, spread, and total markets, with confidence, provenance, and freshness attached to every number instead of a black-box pick.MIT
- AlicenseAqualityCmaintenanceProvides AI assistants with sports model win probabilities and fair odds across nine sports without requiring an API key.354 npmMIT
TDQS
Scored across 6 tools
The tools have mostly distinct purposes: sports list, today's games, upcoming odds, processed odds, event consensus, and API usage. However, 'get_processed_odds' and 'get_event_consensus' could overlap for agents looking for the best line on an event, though descriptions clarify that processed odds gives probabilities and consensus gives a single line.
All tools follow the 'get_' prefix with a resource, which is consistent. The naming is clear and predictable, but some names like 'get_upcoming_odds' and 'get_processed_odds' are similar in structure, which is minor. No mixing of conventions.
With 6 tools, the server is well-scoped for a specialized odds processing service. Each tool serves a distinct function, and the count is within the ideal 3-15 range, providing enough coverage without being bloated.
The tool surface covers listing sports, fetching today's games, upcoming events, processed odds, consensus lines, and API usage. There are minor gaps such as no ability to fetch specific historical games or detailed event details beyond consensus, but the core workflow of getting and processing odds is complete.