sharpapi-mcp
OfficialRelated Servers
Alternatives to sharpapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceProvides AI agents with live, grounded sports data including model probabilities, track records, and European soccer and tennis arbitrage opportunities, so they answer from real numbers instead of stale guesses.1353 npm1MIT

Odds-API MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to access sports betting odds data from 265+ bookmakers across 34 sports, including events, odds, historical data, arbitrage, and value bets.331,057 npm2MIT- FlicenseNot gradedqualityDmaintenanceProvides AI agents with professional-grade tools for expected value calculation, Monte Carlo predictions, historical backtesting, and portfolio risk management in sports betting.-
- AlicenseAqualityDmaintenanceProvides search, trending, odds, arbitrage, and category browsing for prediction markets (Polymarket & Kalshi) via the Model Context Protocol, enabling AI agents to access live market data without API keys.51MIT
- AlicenseBqualityBmaintenanceEnables AI agents to query live and historical sports analytics, consensus betting odds, predictions, scores, schedules, standings, rosters, news, play-by-play, and win probabilities through structured tools and resources.3384 PyPIApache 2.0
- 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.430 npm1MIT
TDQS
Scored across 9 tools
The analytics tools (get_arbitrage, get_ev, get_middles) and discovery tools (list_sports, list_sportsbooks, list_events) each have clearly distinct purposes. The main soft spot is the odds trio: get_odds, get_event_odds, and get_best_odds all return prices, and an agent must read carefully to know that get_odds is paginated/book-row oriented, get_event_odds is event-scoped and unpaginated, and get_best_odds collapses to one row per selection.
All nine tools follow a clean snake_case verb_noun convention (get_*/list_*), with consistent resource naming (odds, event_odds, best_odds, sports, sportsbooks, events). No style mixing or vague verbs.
Nine tools is well within the ideal 3-15 range and each one earns its place: three discovery tools, three odds retrieval views, and three betting-analysis views. Nothing feels redundant or bolted on.
The surface covers the core lifecycle: discover sports/books/events, fetch normalized odds, and derive best-price, arbitrage, EV, and middle views. Minor gaps exist — there is no dedicated market/selection listing tool (markets only appear implicitly in odds rows), no line-movement or historical odds, and no tool to check plan/quota despite several tools being plan-gated.