chesscom-stats-mcp
Related Servers
Alternatives to chesscom-stats-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables querying Chess.com player profiles, ratings, game histories, and leaderboard rankings through a natural language MCP interface.7 npmMIT
- 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.1089MIT
- AlicenseAqualityCmaintenanceMCP server that exposes the Lichess public API through tools for querying player profiles, games, analysis, openings, puzzles, and tournaments, allowing natural-language chess questions without an API key.8MIT
- AlicenseAqualityDmaintenanceEnables querying Chess.com public data including player profiles, stats, games, and club information through natural language.94 npmMIT
- AlicenseBqualityDmaintenanceProvides Chess.com player data integration, enabling AI assistants to fetch real-time chess player profiles and comprehensive statistics including ratings, game counts, and performance metrics from Chess.com's public API.2MIT
- FlicenseBqualityDmaintenanceEnables querying Chess.com player profiles and stats using the Chess.com API.2-
TDQS
Scored across 4 tools
Each tool targets a distinct slice: profile identity, current/best ratings, a monthly aggregate, and a raw recent-games list. The only mild overlap is between month_summary and recent_games, both about played games, but the aggregate-vs-list distinction is spelled out clearly in the descriptions.
Two tools use a get_ verb prefix (get_profile, get_ratings) while the other two are bare noun phrases (month_summary, recent_games). Names are readable and unambiguous, but the set mixes two conventions rather than following one pattern.
Four tools is lean but sensible for a focused Chess.com stats server — identity, ratings, monthly performance, recent games. It sits just under a fully comfortable surface, since users may also want historical or arbitrary-range stats.
Core stats workflows are covered (profile, ratings, month summary, recent games), but there are notable gaps: no arbitrary date-range or archive queries, no fetching a specific game, and no puzzle/tactics or online-status data. Agents can work around some of this but will hit dead ends for historical queries.