Summary
The Cast toolbox, callable mid-conversation.
Debugging a failed transaction usually means pasting hex between four websites. Here the selector lookup, the ABI decode, the balance check and the static call are all reachable from one place, on whichever EVM chain the contract lives.
What it is
A set of Ethereum developer tools exposed over MCP — Cast-style encode and decode operations, a multi-threaded vanity address generator, and RPC access to any EVM-compatible chain.
What you get
- Unknown calldata identified against 4byte.directory, then decoded into its parameters
- ABI encoding and decoding both ways, including a complete function call encoded with its selector
- Function selectors, event selectors and keccak256 hashes computed directly
- Vanity addresses generated to a prefix and a suffix, across up to 16 worker threads, with case sensitivity optional
- Ethereum addresses validated before you send anything to them
- Read-only static calls and balance queries, and transactions sent when you supply a private key — on any of the chains it lists
Requirements
Node — npm install, npm run build, npm start. The read tools need only an RPC endpoint for the chain. Sending a transaction requires a private key, and it is the one operation here that moves funds.
Setup effort
One command — npx blockchain-mcp-server