ChainRPC MCP

Each tool is clearly scoped to a specific chain (btc_ vs evm_) and action (broadcast, decode, estimate, get, call, read). There is no overlap or ambiguity between tools, and even similar-sounding operations like evm_call, evm_readContract, and evm_estimateTransaction are distinct in their purpose and input requirements.

All tools follow a consistent snake_case pattern with chain prefix (btc_ or evm_) followed by a descriptive verb and noun (e.g., btc_getBlock, evm_getLogs). The naming is uniform across both chains, making it predictable and easy to navigate.

At 18 tools, the server sits in the 16-25 range which is considered heavy per the rubric. While the count is justifiable given the dual-chain scope, it could be trimmed or grouped further. It doesn't feel overwhelming, but it's above the typical well-scoped range.

The server covers the essential read and write operations for both Bitcoin and EVM chains, including balances, blocks, transactions, gas estimation, contract reads, and transaction broadcasting. No critical gaps are apparent for a chain RPC server, and all common workflows are supported.