faceit-mcp
Related Servers
Alternatives to faceit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the CopaMind platform via MCP, exposing read-only and write tools for querying match predictions, Monte Carlo simulations, team rankings, and RAG-based explanations, all while maintaining full traceability and reproducibility.1MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to look up live flight status and timetables, create and manage signed-webhook flight subscriptions, inspect delivery attempts and events, and search the API documentation. Tools are exposed to any MCP client such as Claude, Cursor, or VS Code, with read-only, write, and destructive operations clearly marked.1534 npm2MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible LLM clients to access live NBA data, including stats, standings, rosters, scores, and box scores via callable tools.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.7 npmMIT
- FlicenseAqualityBmaintenanceEnables querying FotMob football data including matches, match details, teams, leagues, players, and search through MCP-compatible LLM clients.6-
- AlicenseBqualityCmaintenanceProvides access to Chess.com player data, game records, and public information through standardized MCP interfaces, allowing AI assistants to search and analyze chess information.1093MIT
TDQS
Scored across 64 tools
Tools are largely distinct by entity (game, championship, hub, etc.) and action (get, search), with clear descriptions. Some overlap exists among ranking and leaderboard tools, but they are well-differentiated by parameters and context.
All tools follow a consistent pattern of 'faceit_verb_noun' (e.g., getPlayer, searchHubs). No mixing of casing styles or redundant prefixes. This makes the tool surface predictable.
64 tools is excessive for even a broad platform. While the FACEIT API covers many entities, the tool count overwhelms agents, with many niche tools (e.g., getChampionshipGroupRanking vs getLeaderboard) that could be combined.
The read-only coverage is fairly comprehensive across major entities (players, teams, matches, tournaments, hubs, championships), but there are notable gaps: no write operations, limited filtering on lists, and some missing endpoints like league season listing or live match data.