futpicks-mcp
Related Servers
Alternatives to futpicks-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to access live football data from FotMob, including match stats, team form, injuries, and player workload, without making predictions.101MIT
- AlicenseAqualityCmaintenanceProvides MCP access to PlayerElo's football analytics, including player/coach Elo ratings, match predictions, value bets, and transfer fit scores.17MIT
- FlicenseAqualityCmaintenanceProvides live football data through MCP tools, enabling users to fetch today's matches and top scorers for competitions like the Premier League or World Cup.2-
- AlicenseNot gradedqualityBmaintenanceMCP server that turns real NFL & fantasy data into a decisive edge, offering 70+ tools for draft assistance, start/sit recommendations, trade analysis, playoff odds, and more, with live league integration.MIT
- FlicenseNot gradedqualityBmaintenanceProvides live football data from API-Football over HTTP, enabling queries for upcoming matches, recent results, current standings, injuries, live matches, and team search through MCP tools.-
- AlicenseAqualityCmaintenanceMCP server for the FootballStack football data API. Gives LLM clients and AI agents (Claude, Cursor) access to real football data — fixtures, standings, lineups, live events, shot-level xG with pitch coordinates, and model-derived fair odds.12MIT
TDQS
Scored across 17 tools
Most tools target distinct resources, but there is real overlap among match listing tools (flab_matches_today, flab_matches_upcoming, flab_evaluate_matches) and pick listing/performance tools (flab_picks_today, flab_picks_board, flab_track_record, flab_backtest_run). The descriptions provide helpful differentiators, yet an agent could easily select the wrong member of these clusters.
The consistent 'flab_' prefix and snake_case help readability, but naming conventions are mixed: some tools use verb-first (flab_evaluate_matches, flab_export_picks) while others use noun-first or noun-temporal forms (flab_matches_today, flab_picks_board, flab_backtest_run, flab_ops_run). This inconsistency makes the API slightly harder to predict.
At 17 tools, the server is on the heavier side, but the count is justified by three distinct access tiers: public data, Pro-only analytics, and admin operations. Each tool appears to serve a real workflow, so the size feels reasonable rather than bloated.
The tool surface covers the core domain thoroughly: match discovery and details, published picks and pick boards, historical performance, backtesting, CSV export, on-demand evaluation, health checks, and pipeline operations. There are no obvious dead ends or missing critical operations for a read-oriented sports-data API.