Lumify Sports Intelligence
Related Servers
Alternatives to Lumify Sports Intelligence
- FlicenseBqualityCmaintenanceEnables comprehensive Sleeper Fantasy Football integration with Claude, providing real-time player projections, historical performance analytics, league management, and waiver wire analysis. Supports advanced NFL metrics, lineup optimization, and matchup analysis for fantasy football decision-making.121-
- AlicenseBqualityAmaintenancePrivacy-first MCP server for Strava activities, streams, routes and training data.29171 npm3MIT
Related Servers
- AlicenseAqualityCmaintenanceProvides AI assistants with sports model win probabilities and fair odds across nine sports without requiring an API key.360 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides comprehensive sports intelligence including live scores, standings, schedules, betting odds, news, highlights, and more via SSE transport.-

PropLineofficial
AlicenseAqualityAmaintenanceLive sports betting odds, cross-book +EV, and graded player-prop resolution across 13 books.111,893 npm1MIT- 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.1344 npm1MIT
- 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
- AlicenseAqualityDmaintenanceProvides AI-powered sports analytics for Daily Fantasy Sports (DFS) with real-time player projections, lineup optimization, live odds aggregation from multiple sportsbooks, and SHAP-based explainability to understand recommendation reasoning.41MIT
TDQS
Scored across 10 tools
The tools split cleanly across events, odds, teams, players, and seasons, and there are explicit cross-references (e.g., get_event vs batch_get_events vs list_events/query_events). The only mild overlap is that get_odds, get_odds_history, and get_splits all relate to betting data, but each targets a distinct data type: current lines, line movement, and splits.
Use of get_/list_/batch_/query_ conventions is mostly consistent: get_event, get_odds, get_player; list_teams, list_seasons; batch_get_events, query_events. One slight inconsistency is get_player_events (verb_noun_verb rather than get/get/list pattern) and list_teams/list_seasons vs batch_get_events, but overall naming is predictable.
10 tools is well-scoped for a sports intelligence API covering events, odds, teams, players, and seasons. Each tool maps to a distinct resource or data type, with no obvious bloat or redundancy.
The surface covers event retrieval (single, batch, query), odds, splits, teams, players, player events, and seasons. Notable gaps: there is no tool for listing or searching sports/leagues directly (list_sports is referenced but not present), and no get_team tool even though list_teams says to use get_team for full detail. Also search_players is referenced but not present. These are minor omissions since the described tools still cover core read-only workflows, but the cross-references reveal missing dependencies.