approve_token_spending
Approve a spender (contract) to spend tokens on your behalf. Required before interacting with DEXes, lending protocols, etc.
LABSCO SUMMARY
The read half needs no key at all; the write half is where you hand over a wallet.
Balances, ENS lookups, receipts and Multicall3 batching run against public RPC, so an agent can inspect chain state without ever holding a key. The moment you want transfer_native, write_contract or a signature, that same server needs a private key or mnemonic in its environment, and the tool list draws no line between the two halves at call time. ABI auto-fetch smooths over contracts you did not write, but it depends on ETHERSCAN_API_KEY and falls back to common functions when a contract is unverified.
What it is
An RPC and wallet client for EVM networks: chain and block reads, ERC20, ERC721 and ERC1155 balances, contract calls in both directions, and message signing.
What you get
- Network-level reads: chain id and current block, the list of supported networks, and base, standard and fast gas prices
- Balances for any address — native token, ERC20, and ERC1155 by token id — plus the allowance an owner has granted a spender
- ENS resolution in both directions, name to address and address back to name
- A transaction by hash with its receipt, confirmation status, gas used and logs, and a call that polls until the number of confirmations you set
- Contract interaction with the ABI fetched from a block explorer when you do not supply one: read-only calls, state-changing calls, and many reads batched into a single RPC request through Multicall3
- Transfers and approvals from the configured wallet — native token, ERC20, and the approval a DEX or lending protocol needs first
- Signatures from the configured wallet: an arbitrary message for SIWE-style authentication, or EIP-712 structured data for permits and meta-transactions
Requirements
For the read half, a reachable network and nothing else. Transfers, approvals, write_contract and both signing tools need a wallet configured from a private key or mnemonic, and automatic ABI lookup needs ETHERSCAN_API_KEY.
Setup effort
One command — npx @mcpdotdirect/evm-mcp-server
USE CASES
01
Checking what an address actually holds
Native balance, ERC20 balances and ERC1155 balances by token id are separate calls, so a portfolio view means several reads — batch them into one RPC request rather than paying the round trips.
02
Working out whether a transaction went through
The transaction tells you what was submitted, the receipt tells you whether it was mined and what gas it burned, and the wait call blocks until the number of confirmations you decide is enough.
03
Reading a contract you did not write
Pull the ABI from a block explorer to see what the contract exposes, then call its read-only functions. Unverified contracts fall back to the common functions rather than failing outright.
04
Moving funds under agent control
Native and ERC20 transfers both run from the configured wallet, and anything that hands spending power to a protocol needs an approval first. This is the half of the tool list that requires a private key or mnemonic to be present.
05
Signing in to a dapp or issuing a permit
An arbitrary signed message covers SIWE-style authentication; EIP-712 structured data covers permits, meta-transactions and anything a protocol expects in a typed envelope. Both use the configured wallet.
06
Timing a submission against gas
Base, standard and fast prices come back together, alongside the chain's current block, so an agent can decide whether to send now or wait without leaving the tool loop.
25 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_allowance
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_balance
Get the native token balance (ETH, MATIC, etc.) for an address
get_block
Get block details by block number or hash
get_chain_info
Get information about an EVM network: chain ID, current block number, and RPC endpoint
get_contract_abi
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.
get_erc1155_balance
Get ERC1155 token balance for an address
get_gas_price
Get current gas prices (base fee, standard, and fast) for a network
get_latest_block
Get the latest block from the network
get_nft_info
Get information about an ERC721 NFT including metadata URI
get_supported_networks
Get a list of all supported EVM networks
get_token_balance
Get the ERC20 token balance for an address
get_transaction
Get transaction details by transaction hash
get_transaction_receipt
Get transaction receipt (confirmation status, gas used, logs). Use this to check if a transaction has been confirmed.
get_wallet_address
Get the address of the configured wallet. Use this to verify which wallet is active.
lookup_ens_address
Lookup the ENS name for an Ethereum address (reverse resolution)
multicall
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.
read_contract
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.
resolve_ens_name
Resolve an ENS name to an Ethereum address
sign_message
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_data
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.
transfer_erc20
Transfer ERC20 tokens to an address. Uses the configured wallet.
transfer_native
Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet.
wait_for_transaction
Wait for a transaction to be confirmed (mined). Polls the network until confirmation.
write_contract
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).
BEFORE YOU INSTALL
What to know first
Tools you get
25 tools when we connected. All tools register, but the six wallet tools need EVM_PRIVATE_KEY or EVM_MNEMONIC, and get_contract_abi needs ETHERSCAN_API_KEY.
Requires
- npx on PATH
- Node.js 20.0.0 or later
CONTEXT COST
Moderate Standing cost
Rated by the size of the 25 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @mcpdotdirect/evm-mcp-serverMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"evm-mcp-server": {
"command": "npx",
"args": [
"-y",
"@mcpdotdirect/evm-mcp-server"
]
},
"evm-mcp-http": {
"command": "npx",
"args": [
"-y",
"@mcpdotdirect/evm-mcp-server",
"--http"
]
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add evm-mcp-server npx @mcpdotdirect/evm-mcp-serverAny MCP client — SSE
ANY MCP CLIENT — SSE · JSON
{
"mcpServers": {
"evm-mcp-sse": {
"url": "http://localhost:3001/sse"
}
}
}
