kashrock-mcp
OfficialRelated Servers
Alternatives to kashrock-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP-compatible clients to access sports betting odds, player props, prediction markets, live previews, coverage checks, and ParlayAPI account signup through native tools.2297 PyPIMIT
- AlicenseBqualityDmaintenanceMCP-compatible server that gives AI agents access to alternative sports data across 30+ leagues — odds, events, probabilities, settlement, and futures for prediction markets, DFS platforms, and sportsbooks.298 npmMIT
- AlicenseAqualityAmaintenanceLive sports betting player props MCP server covering NBA, MLB, NFL, NHL, NCAA, and soccer. Unified from real sportsbooks into one REST API and a real MCP server (Streamable HTTP). Free tier, no card required.5MIT
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to DraftKings DFS lobby data, including slates, contests, salaries, and roster rules, via MCP.-
- AlicenseAqualityBmaintenanceA unified MCP server that aggregates 32 sports API providers into a single service, providing 336 tools for scores, stats, odds, esports, and more across 70+ sports.10066 npm33MIT
- AlicenseNot gradedqualityBmaintenanceProps-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
TDQS
Scored across 46 tools
Several tools have heavily overlapping surfaces, such as get_props/get_player_props/get_player_snapshot, get_lines/get_best_lines/get_moneylines/get_live_odds, and get_live_games/get_live_boxscore (which also lists live games when game_id is omitted). Descriptions add caveats, but with 46 similarly named read tools an agent will often struggle to pick the right one.
The vast majority of tools follow a get_/list_/search_/research_ + noun snake_case pattern, and there is no mixed casing. Minor deviations like login, whoami, explain_error, and suggest_build are still readable and conventional, though the abundance of get_lines/get_live_odds/get_moneylines/get_best_lines makes names semantically confusing.
At 46 tools, this is far beyond the healthy 3-15 range and falls into the 'too many' category. Many tools could be consolidated, especially the live-game listing, props variants, and lines/odds families, which would reduce navigation burden without losing capability.
The surface covers the domain well: plan/auth, sports/books/markets catalogs, match scheduling, player search and stats, props, odds, live telemetry, results, media, and research tapes. Minor gaps exist—no tournament/event listing and no direct single-prop detail endpoint—but agents can work around them with existing tools.