project-cpu-mcp
Related Servers
Alternatives to project-cpu-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceAn MCP server that provides cryptocurrency project data to AI agents11MIT
- AlicenseBqualityDmaintenanceA Minecraft MCP Server powered by Mineflayer API. It allows to control a Minecraft character in real-time, allowing AI assistants to build structures, explore the world, and interact with the game environment through natural language instruction82250 npm754Apache 2.0
- AlicenseAqualityCmaintenanceMCP server that lets AI agents browse, create, and submit tasks on Taskmarket, and check wallet balances, using the official CLI for secure key handling.9293 npmAGPL 3.0
- AlicenseNot gradedqualityAmaintenanceLocal MCP server that lets AI agents control a Minecraft Forge 1.20.1 NPC to chat, move, gather, craft, build, fight, and manage inventory in a single-player world.2MIT
- AlicenseAqualityCmaintenanceMCP server for the RustChain blockchain and BoTTube video platform, enabling AI-agent-based token earning through model context protocol and proof-of-antiquity.252MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Golem framework that lets AI agents control a Minecraft character, providing tools for movement, interaction, inventory, crafting, and executing Shem scripts.70 npmMIT
TDQS
Scored across 71 tools
Most tools target a distinct resource+action pair, and the detailed descriptions make even similar status/claim tools distinguishable. The main ambiguity comes from the market cluster (cpu_get_markets, cpu_get_market_index, cpu_get_cell_market) and the overlapping 'my listings/offers/lots' set, which could mislead an agent scanning names quickly.
The server follows a consistent cpu_<verb>_<noun> snake_case pattern across nearly all tools, with coherent verbs like get, list, create, quote, and set. Minor outliers such as cpu_onboarding, cpu_persona, and cpu_next_hops, plus compound names like cpu_get_my_offers_received, prevent a perfect score.
71 tools is far beyond the 25+ threshold and makes the server feel bloated as a single MCP, even though the underlying game has many subsystems. The surface would be much more coherent split into focused servers for onboarding, production, transport, marketplace, land trading, and syndicates.
The tool set covers the full game loop: onboarding, authentication, land/reveal/build, mining and crafting, transport, resource marketplace, NFT land marketplace, syndicates, and token swaps/mints. Minor gaps like bulk operations and deeper syndicate member management exist, but agents can complete core workflows without dead ends.