WSDC Points MCP Server
Related Servers
Alternatives to WSDC Points MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read a Concept2 Logbook account through MCP, covering training summaries, personal bests, workout lists, splits, intervals, stroke data and profile details. Access is read-only via an API key created after signing in with Concept2.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query read-only requirements and test data to find uncovered requirements, failing tests, coverage summaries, and qualification reports through MCP tools.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to query the author's career, projects, publications, and technical documents through read-only MCP tools.-
- AlicenseNot gradedqualityBmaintenanceProvides read-only MCP tools for AI agents and coding assistants to search podcast transcripts and episode metadata, retrieve transcript excerpts, and generate citations. It requires no login or API key.1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to query the FACEIT platform for players, matches, hubs, and tournaments through typed MCP tools generated from the FACEIT Data API v4.64MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and analyze self-hosted real-estate public-records data through 20 read-only MCP tools, including property search, foreclosure and distress signals, comps, market context, and optional license-gated deal scoring.MIT
TDQS
Scored across 9 tools
Each tool targets a clearly distinct entity/action pair: dancer search vs. dancer profile vs. dancer results, and event search vs. event results. The descriptions explicitly cross-reference which tool to use next (e.g., 'Use the WSDC ID with the other dancer tools'), leaving no realistic chance of misselection.
All nine tools follow a strict snake_case verb_noun pattern using only two verbs (search_/get_) matched to the correct semantics. No camelCase, no vague verbs like 'process' or 'handle'.
Nine tools is well within the ideal 3-15 range and each maps to a distinct query type (search, profile, results, stats, level-ups, rules, metadata). No filler or redundant tools are present.
The read-only registry domain is well covered: entity search, detail views, results, aggregate stats, level-up tracking, rules lookup, and data freshness metadata. Minor gaps exist (e.g., no cross-dancer comparison or points-to-next-division projection), but agents can work around them by combining existing tools.