cpu-game-mcp
Related Servers
Alternatives to cpu-game-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.10023 npm42-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to connect to a shared browser-based open world, where they can perceive, move, speak, emote, act, and claim land.2 npm1-
- AlicenseAqualityCmaintenanceAn MCP server that lets AI agents build on GenLayer by searching documentation, inspecting contracts and transactions over RPC, and scaffolding, linting, and testing Intelligent Contracts.4620 npm1MIT
- AlicenseAqualityDmaintenanceThe first blockchain & cryptocurrency MCP server that connects AI agents to Ethereum, Solana, Bitcoin, and cryptocurrency markets.916 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-powered chat and DeFi operations (swap, transfer) via MCP-compliant tools, integrating with LLMs for onchain actions.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceA powerful toolkit that enables seamless interaction with EVM-compatible networks through natural language processing and AI assistance, allowing users to manage wallets, launch tokens, and interact with blockchain networks.11 npmMIT
TDQS
Scored across 38 tools
Each tool targets a clear resource or action: quote/execute pairs preview before committing, get/list tools separate single-item lookup from browsing, and mining/craft/transport/market systems each have their own lifecycle tools. Even the marketplace reads (get_markets vs list_lots) are explicitly differentiated as overview vs drill-down.
The cpu_ prefix plus snake_case applies everywhere and most names follow a verb_noun pattern (cpu_get_cell, cpu_create_lot, cpu_claim_craft). Minor deviations like cpu_authenticate, cpu_withdraw, and cpu_next_hops are slightly less pattern-consistent but do not create real confusion.
38 tools is a heavy surface, well above the 16-25 range already considered borderline. The game's many subsystems partly justify the count, but an agent facing this many options will struggle with selection and context load.
The tool set covers the full game loop: authenticate, mint, reveal, build, demolish, mine, craft, claim, transport, finalize deliveries, marketplace create/buy/cancel, fee setting, and ETH/CPU swap. Each major workflow has preview, execution, status, and claim/finalize steps, leaving no obvious dead ends.