chessvox-mcp
Related Servers
Alternatives to chessvox-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to look up Lichess players, review their recent games and flagged mistakes, and answer chess questions using Lichess's own server analysis, cloud evaluations, and Syzygy tablebase rather than guessing. Also serves daily and by-id puzzles (with solutions hidden until requested) and opening explorer statistics, returning explicit "not available" responses when Lichess has no data.9MIT
- AlicenseBqualityAmaintenanceEnables natural-language access to Chess.com's public API, exposing player, club, tournament, puzzle, and leaderboard data through tools and resources without authentication.3039 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query Chess.com's public API for player profiles, stats, game archives, online status, clubs, and titled players, and to download game PGNs.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to retrieve Chess.com player profiles, statistics, and daily puzzles through the Model Context Protocol.13 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to explore player profiles, ratings, game archives, leaderboards, clubs, and puzzles via the Chess.com API.2MIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides access to Chess.com's public API, allowing AI assistants to fetch player information and statistics.-
TDQS
Scored across 3 tools
All three tools target distinct resources: a single daily puzzle, a batch of mate-in-1 drills, and a list of starter repertoires. The two puzzle tools share the same output shape (FEN + UCI solution), so an agent skimming could momentarily confuse them, but the descriptions make the daily-vs-batch distinction explicit.
All names follow a uniform pattern: consistent `chessvox_` server prefix plus snake_case descriptive noun phrases. No mixed conventions or vague verbs anywhere in the set.
Three tools is lean but each covers a genuinely different content type (daily content, drill batches, opening repertoires), so nothing feels redundant. It is on the thin side for a puzzle/opening domain, but not inappropriately so for a narrow read-only content API.
The surface covers puzzles and a repertoire listing, but there is no way to fetch a repertoire's full line tree (only preview moves), no puzzle lookup by rating or theme, and no answer-checking tool despite that being a stated use case. Agents can work around these limits but will hit visible dead ends.