draftkingsapi-mcp
Related Servers
Alternatives to draftkingsapi-mcp
No user-submitted related servers found.
Related Servers
- 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.33358 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.297 npm1MIT

sharpapi-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to query live sports betting odds, best prices, arbitrage, +EV bets, and middles directly through Model Context Protocol tools.963 npmMIT- AlicenseBqualityDmaintenanceProvides 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.1368 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query MLB and NCAA Division I baseball data, including pitch-by-pitch and plate-appearance records, stats, ratings, sportsbook odds, player props, and prop history, through natural-language tool calls.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to query live sports betting data including odds, edges, arbitrage opportunities, player/team stats, and reference data using the SportWizzard API.20132 npmMIT
TDQS
Scored across 23 tools
Most tools map to distinct resources, but several near-pairs exist: get_public_board vs get_pick6_projections (capped/keyless vs full keyed board), get_public_sportsbook vs get_odds, and get_compare vs get_compare_books. The three meta tools (get_coverage, get_history_coverage, get_status) and four history tools (get_odds_history, get_pick6_history, get_pick6_line_history, get_public_line_moves) also require careful reading to separate. Descriptions do provide enough signal to disambiguate, but selection errors are plausible.
All 23 tools use a uniform get_ prefix with snake_case noun phrases, giving a highly predictable surface. Minor deviations exist in word ordering and qualifiers (get_stats_player_games vs get_dfs_players, get_pick6_history vs get_pick6_line_history, the 'public_' keyless marker), but the pattern is still readable.
23 tools is on the heavy side and largely driven by the free/keyless vs API-key duplication of the same underlying data (public_board vs pick6_projections, public_sportsbook vs odds). The breadth across Pick6, sportsbook, DFS, stats and analysis partially justifies the count, but the surface feels bloated.
Coverage is broad: sportsbook events/odds/history, Pick6 projections and line history, DFS slates/contests/players, player and game stats, cross-book comparison, EV and arbitrage, plus meta tools for coverage, status and credit costs. Gaps are minor, e.g. no explicit markets/futures enumeration or contest-level result lookup, but core workflows have no dead ends.