fanduelapi-mcp
Related Servers
Alternatives to fanduelapi-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceProvides MCP clients with sportsbook prices and pick'em lines across DraftKings, FanDuel, BetRivers, PrizePicks, Underdog and Pick6, including capture times and line history. Two tools work without an account, with the remainder requiring a free API key.9MIT- AlicenseNot gradedqualityCmaintenanceProps-first sports odds API with a hosted MCP server. Live odds and player props (moneyline, spreads, totals) across US sportsbooks, normalized to JSON. Tools: get_odds, get_props, get_events, get_books. API-key auth, free tier.MIT No Attribution
- AlicenseNot gradedqualityCmaintenanceOfficial MCP server for the SportsGameOdds API. Query live and pre-match odds, scores, player props, results and settlement across 85+ sportsbooks and 67+ leagues, with endpoint discovery, documentation search and usage monitoring built in.1,031 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to access FantasyPros data through tools for injury news, player lookup, consensus rankings, and projections.1MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible clients to access sports betting odds, player props, prediction markets, live previews, coverage checks, and ParlayAPI account signup through native tools.221MIT

novigapi-mcpofficial
AlicenseBqualityCmaintenanceEnables MCP clients to access live sports betting market data, including markets and order books, player props, line history, fair prices, closing-line value, +EV and arbitrage comparisons, and devig calculations.36MIT
TDQS
Scored across 29 tools
Most tools target distinct resources (props, events, line history, EV, arbitrage, watch CRUD, billing), but there are outright duplicates: search_docs vs search and fetch_doc vs fetch are functionally the same pair, differing only in 'shape'. There is also mild overlap between list_events, odds_board and game_report (all can surface games/lines), so an agent must read descriptions carefully to pick correctly.
The dominant pattern is snake_case verb_noun (list_watches, get_subscription, cancel_subscription), but a substantial second family of bare-noun analytics names exists (line_move, prop_history, recent_changes, odds_board, game_report, positive_ev, arbitrage) plus bare verbs (search, fetch). Within-set pluralization is also odd (create_watches/get_watches vs get_subscription), so conventions are mixed though still readable.
At 29 tools this is a heavy surface for an odds API, and a meaningful share is not earning its place: two doc-search aliases, a three-step signup flow, and a separate cancellation trio. The domain is broad (odds data + billing + onboarding), but the set could be trimmed toward the 15-20 range without losing capability.
Coverage is strong: docs search, discovery (events/odds board/game report), prop data with history and change feed, analytics (EV, arbitrage, book comparison), watchlist CRUD, signup and subscription lifecycle, feedback and onboarding. Gaps are minor — no endpoint for enumerating stat types, players/teams, or managing watch notification delivery — and are workable around via existing filters.