bb-mcp
Related Servers
Alternatives to bb-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables read-only access to Sleeper fantasy sports data, including users, leagues, rosters, matchups, transactions, drafts, players, trending activity, playoff brackets, traded picks, and sport state via MCP tools.18-
- AlicenseAqualityCmaintenanceEnables read-only access to public Swedish sports competition data, including federations, districts, schedules, results, standings, team searches, matches by date, and detailed match protocols. It provides these capabilities through MCP tools without requiring login, a browser, or credentials.9MIT
- FlicenseNot gradedqualityCmaintenanceProvides read-only access to Sleeper fantasy football data including user info, leagues, rosters, matchups, and NFL state through MCP tools.-
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to DraftKings DFS lobby data, including slates, contests, salaries, and roster rules, via MCP.-
- AlicenseNot gradedqualityBmaintenanceEnables read-only, keyless access to hosted job search through nine MCP tools for browsing postings, matching candidates, retrieving job details and discussion threads, resolving locations, listing companies, getting stats, and performing deep-research search/fetch.313 npmMIT
- AlicenseAqualityBmaintenanceEnables read-only retrieval of Ekşi Sözlük’s trending topics, topic search results, sorted entries, channel topics, and yesterday’s most-liked entries via MCP tools.6MIT
TDQS
Scored across 29 tools
Most tools target a distinct resource+action, and descriptions clarify the fine distinctions (e.g. get_arena_attendance vs get_team_arena vs get_team_facilities, or get_team_training vs get_team_training_history). The riskiest overlaps are the analytics cluster (get_team_stats, scout_team, get_match_shooting, get_boxscore) and get_team_roster vs get_player, but the "use only when explicitly asked" guidance mitigates misselection.
Nearly everything follows a snake_case verb_noun pattern (get_*, search_*, scout_*). The one wrinkle is that the get_team_* prefix is overloaded: some of those tools operate on any club (roster, schedule, stats, arena) while others are own-team-only (training, staff, facilities, economy, salaries), and get_arena_attendance sits outside that prefix.
29 tools is heavy for a single server and pushes past the comfortable 3-15 range. The domain is genuinely broad (teams, players, market, matches, competitions, countries, national teams) so most tools do map to unique data, but sub-resources like facilities/economy/salaries/staff could plausibly be consolidated into a team-finances or team-info call.
Coverage of the read surface is strong: team info/roster/schedule/stats/training/finances, market search plus auction detail, match header/boxscore/events/shooting, standings, seasons, countries, leagues and national teams. Notable gaps remain on the player side (no season-by-season player stats or player career/history, no transfer/bid actions) and no league-level fixture listing, but these are minor for a read-only companion API.