EVM 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 |
|---|---|
| get_wallet_addressA | Get the address of the configured wallet. Use this to verify which wallet is active. |
| get_chain_infoA | Get information about an EVM network: chain ID, current block number, and RPC endpoint |
| get_supported_networksA | Get a list of all supported EVM networks |
| get_gas_priceA | Get current gas prices (base fee, standard, and fast) for a network |
| resolve_ens_nameA | Resolve an ENS name to an Ethereum address |
| lookup_ens_addressA | Lookup the ENS name for an Ethereum address (reverse resolution) |
| get_blockB | Get block details by block number or hash |
| get_latest_blockB | Get the latest block from the network |
| get_balanceA | Get the native token balance (ETH, MATIC, etc.) for an address |
| get_token_balanceA | Get the ERC20 token balance for an address |
| get_allowanceA | Check the allowance granted to a spender for a token. This tells you how much of a token an address can spend on your behalf. |
| get_transactionB | Get transaction details by transaction hash |
| get_transaction_receiptA | Get transaction receipt (confirmation status, gas used, logs). Use this to check if a transaction has been confirmed. |
| wait_for_transactionA | Wait for a transaction to be confirmed (mined). Polls the network until confirmation. |
| get_contract_abiA | Fetch a contract's full ABI from Etherscan/block explorers. Use this to understand verified contracts before interacting. Requires ETHERSCAN_API_KEY. Supports 30+ EVM networks. Works best with verified contracts on block explorers. |
| read_contractA | Call read-only functions on a smart contract. Automatically fetches ABI from block explorer if not provided (requires ETHERSCAN_API_KEY). Falls back to common functions if contract is not verified. Use this to query contract state and data. |
| write_contractA | Execute state-changing functions on a smart contract. Automatically fetches ABI from block explorer if not provided (requires ETHERSCAN_API_KEY). Use this to call any write function on verified contracts. Requires wallet to be configured (via private key or mnemonic). |
| multicallA | Batch multiple contract read calls into a single RPC request. Significantly reduces latency and RPC usage when querying multiple functions. Uses the Multicall3 contract deployed on all major networks. Perfect for portfolio analysis, price aggregation, and querying multiple contract states efficiently. |
| transfer_nativeA | Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet. |
| transfer_erc20A | Transfer ERC20 tokens to an address. Uses the configured wallet. |
| approve_token_spendingA | Approve a spender (contract) to spend tokens on your behalf. Required before interacting with DEXes, lending protocols, etc. |
| get_nft_infoA | Get information about an ERC721 NFT including metadata URI |
| get_erc1155_balanceB | Get ERC1155 token balance for an address |
| sign_messageA | Sign an arbitrary message using the configured wallet. Useful for authentication (SIWE), meta-transactions, and off-chain signatures. The signature can be verified on-chain or off-chain. |
| sign_typed_dataA | Sign structured data (EIP-712) using the configured wallet. Used for gasless transactions, meta-transactions, permit signatures, and protocol-specific signatures. The signature follows the EIP-712 standard. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| prepare_transfer | Safely prepare and execute a token transfer with validation checks |
| diagnose_transaction | Analyze transaction status, failures, and provide debugging insights |
| analyze_wallet | Get comprehensive overview of wallet assets, balances, and activity |
| audit_approvals | Review token approvals and identify security risks from unlimited spend |
| fetch_and_analyze_abi | Fetch contract ABI from block explorer and provide comprehensive analysis |
| explore_contract | Analyze contract functions and state without requiring full ABI |
| interact_with_contract | Safely execute write operations on a smart contract with validation and confirmation |
| explain_evm_concept | Explain EVM and blockchain concepts with examples |
| compare_networks | Compare multiple EVM networks on key metrics and characteristics |
| check_network_status | Check current network health and conditions |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported_networks | Get list of all supported EVM networks and their configuration |
TDQS
Scored across 25 tools
Most tools have distinct purposes, but there is some overlap between get_block and get_latest_block, and between get_contract_abi and read_contract/write_contract's ABI fetching. The descriptions help clarify, but an agent might occasionally hesitate between these pairs.
Tool names follow a highly consistent verb_noun or verb_noun_noun pattern throughout, such as get_balance, transfer_erc20, and sign_message. There are no deviations in style, making them predictable and easy to parse.
With 25 tools, the count is on the high side for an MCP server, bordering on heavy. While the domain (EVM interactions) is broad, this many tools could overwhelm agents or lead to redundancy, though it covers many use cases.
The tool set provides comprehensive coverage for EVM operations, including token transfers, contract interactions, network queries, and wallet management. It supports full workflows from reading to writing, with no obvious gaps in the domain.