rttf-mcp
Related Servers
Alternatives to rttf-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides access to the r.ttw.ru table tennis rating site, enabling searches for players, matches, head-to-head encounters, and tournaments via MCP tools.5MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and terminal users to search players and tournaments, read tournament pages as structured data, and retrieve Austrian championship leagues without login. Also supports checking and, after confirmation, entering team match reports against club rosters and the public results site.MIT
- FlicenseBqualityDmaintenanceEnables querying Chess.com player profiles and stats using the Chess.com API.2-
- FlicenseAqualityDmaintenanceProvides programmatic access to CTFtime.org data for retrieving information about CTF competitions, team rankings, and event results. It enables users to search for upcoming events, analyze team performance, and access historical competition data through a standardized interface.94-
- AlicenseAqualityCmaintenanceEnables to access VEX Robotics Competition data including teams, events, rankings, skills scores, and forum via RobotEvents API.159 npm2MIT
- FlicenseBqualityDmaintenanceEnables querying volleyball match, team, and tournament data from VolleyballWorld API through SQL queries on a SQLite database.1-
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: single player, single hall, single tournament, player listing, tournament search. There is no meaningful overlap; get_player/list_players and get_tournament/search_tournaments are clearly separated by entity vs collection.
All tools follow a consistent lower_snake_case verb_noun pattern: get_ for individual resources and list_/search_ for collection queries. The naming convention is uniform and predictable.
Five tools is well-scoped for a read-only sports data domain covering players, halls, and tournaments. Each tool earns its place and there is no bloat or obvious missing core resource.
The core domain is well covered: player profiles, halls, tournament standings, player ratings listing, and tournament search. Minor gaps exist due to intentional site restrictions, such as no match-level data, no player name search, and no paginated tournament search, but these are clearly documented workarounds rather than accidental omissions.