Blockchain MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate-vanity-addressB | Generate Ethereum addresses matching specified prefix and suffix patterns with concurrent computation |
| validate-ethereum-addressC | Validate the validity of an Ethereum address |
| 4byteC | Get function signatures for the given selector from 4byte.directory |
| 4byte-decodeC | Decode ABI-encoded calldata using 4byte.directory |
| abi-encodeC | encode function parameters with abi |
| abi-encode-with-signatureC | encode function call with abi |
| abi-decodeC | decode abi encoded data |
| sigC | get function selector |
| event-sigC | get event selector |
| keccak256B | calculate keccak256 hash |
| static-callA | Make a static call to a smart contract on any EVM-compatible chain (read-only) |
| send-transactionB | Send a transaction to a smart contract on any EVM-compatible chain (requires private key) |
| get-balanceB | Get the balance of an address on any EVM-compatible chain |
| list-chainsB | List all supported EVM-compatible chains and their configurations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have distinct purposes, but there is some overlap between 'abi-decode' and '4byte-decode' (both decode ABI-encoded data) and between 'sig' and 'event-sig' (both get selectors). The descriptions clarify that '4byte-decode' uses an external service while 'abi-decode' is generic, and 'sig' is for functions while 'event-sig' is for events, but an agent might still confuse them initially.
The naming is mixed with kebab-case (e.g., '4byte-decode'), snake_case (e.g., 'keccak256'), and hyphenated phrases (e.g., 'generate-vanity-address'). There is no consistent verb_noun pattern; some tools use verbs like 'get' or 'validate', while others are noun-based like 'sig' or 'event-sig'. However, the names are generally readable and descriptive.
With 14 tools, the count is well-scoped for a blockchain utility server covering ABI encoding/decoding, address generation, balance checks, transaction handling, and chain management. Each tool appears to serve a specific function without obvious redundancy, fitting within the typical 3-15 range for such a domain.
The tool set covers core blockchain operations like ABI handling, address validation, balance queries, transaction sending, and static calls. Minor gaps include lack of tools for transaction signing without sending, or for deploying contracts, but agents can likely work around these with existing tools like 'send-transaction' and 'abi-encode'.