scorezilla-mcp
Related Servers
Alternatives to scorezilla-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceOfficial MCP server for exerciseapi.dev — give your AI coding agent direct access to 2,198+ vetted exercises across 12 categories.17 npm3MIT

Nhost MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceOfficial MCP server for the Nhost backend platform. Manage Postgres data, GraphQL, auth, storage, migrations and Hasura metadata via AI assistants.5MIT- AlicenseAqualityBmaintenanceOfficial MCP server for creating and managing AI UGC video ads. Browse assets, estimate credit costs, generate videos, and retrieve completed outputs through eleven typed tools.1122 npmMIT

BlazingCDN-MCPofficial
AlicenseAqualityBmaintenanceOfficial MCP server for BlazingCDN - AI agents (Claude, Cursor, Windsurf) manage CDN resources, purge cache, query metrics, domains, Cloud Storage and Video CDN2943 npm2MIT- AlicenseNot gradedqualityCmaintenanceOfficial MCP server for the Lacuna Music API. Generate AI music — full songs with vocals and lyrics, or instrumentals — with style prompts, task status polling, and audio downloads.5MIT
- AlicenseAqualityCmaintenanceOfficial MCP server for the Perplexity API Platform, enabling AI assistants to perform real-time web search, reasoning, and deep research using Sonar models.416,084 npmMIT
TDQS
Scored across 11 tools
Most tools have clearly distinct resource+action targets, and descriptions explicitly separate bootstrap_leaderboard (brand-new game) from create_game/create_board (existing games). The main overlap is bootstrap_leaderboard versus the create_game + create_board + mint_key + get_sdk_snippet sequence, but state-based guidance reduces misselection risk.
All tool names use snake_case with a leading verb and a clear noun target (create_board, list_games, update_board_config, get_keys). Minor compound variations like get_board_top_n and update_game_config remain predictable and readable.
11 tools is well within the sweet spot for a leaderboard service, and each tool covers a distinct part of the workflow: onboarding, game/board management, config, keys, snippets, and score reads. No tool appears redundant or padded.
The surface covers create/read/update for games and boards, key minting/retrieval, integration snippets, and score reads, which supports the main developer workflow. However, there are no delete/cleanup operations for games or boards, and key rotation/revocation is intentionally delegated to the dashboard, leaving some lifecycle gaps.