
Evmcp
io.github.siriuslatticePublished by GitHub account siriuslatticev0.1.3Updated Oct 24, 2026
Multi-chain EVM blockchain data with companion smart contracts
Overview
Read-only MCP server that gives an assistant 28+ tools to query EVM on-chain data across Base, Optimism, Avalanche, Celo and Arbitrum via Alchemy RPC.
- What you can do
- Read balances: native, ERC20, allowance and multi-chain balance lookups
- Inspect blocks and transactions: fetch blocks by hash or number, latest block, transactions, receipts and ABI-based decoding
- Query contracts and tokens: read-only contract calls, bytecode checks, storage slots, ERC20 metadata and event logs
- Compare gas: current gas prices, gas estimates, cross-chain gas comparison and cheapest-chain recommendations
- Resolve ENS names and reverse-lookup addresses on Ethereum L1
- Run batch and cross-chain queries through Multicall3 and companion contracts, plus chain info and RPC health checks
- When to use it
- Useful when you want an assistant to answer questions about wallets, tokens, contracts, transactions or gas costs on the five supported EVM chains without writing RPC code yourself. It suits read-only research, wallet and contract inspection, and cross-chain comparisons.
- Requirements
- Runs locally over stdio, typically via npx. Needs an Alchemy API key in ALCHEMY_API_KEY, or individual RPC URL overrides for each chain. Optional settings cover cache TTL, log level, testnets, HTTP transport and x402 payment gating. Network access to the RPC endpoints is required.
Installation
In SourceWeft
- Open Evmcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
evmcp
EVM + MCP — give your AI assistant blockchain superpowers.
MCP server providing real-time access to on-chain data across Base, Optimism, Avalanche, Celo, and Arbitrum, with companion smart contracts deployed on-chain for batch queries and cross-chain data.
How it Works
EVMCP implements the Model Context Protocol (MCP), a standard that lets AI assistants call external tools. When connected, your AI assistant gains 28 read-only blockchain tools it can invoke to query balances, decode transactions, compare gas prices, and more across five EVM chains.
What sets EVMCP apart is its companion smart contracts — four Solidity contracts deployed on Avalanche and Celo that enable batch queries via Multicall3, an on-chain tool registry, event aggregation, and cross-chain balance caching. The MCP server reads from these contracts; all write operations are performed separately by an admin CLI.
Quick Start
With Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
With Claude Code
Supported Chains
Ethereum mainnet (chain ID 1) is also supported for ENS resolution only.
Tools (29 total)
Balance (3)
Block (3)
Transaction (3)
Contract (3)
Token (2)
Gas (3)
ENS (2)
Events (2)
Chain and Health (3)
Batch (1)
Cross-Chain (2)
Registry (1)
Optimizer (1)
Resources (4)
Supported chain IDs for templated resources: 8453 (Base), 10 (Optimism), 43114 (Avalanche), 42220 (Celo), 42161 (Arbitrum).
Prompts (4)
Companion Contracts
Four Solidity contracts are deployed on Avalanche and Celo. The MCP server reads from these contracts to provide batch queries, on-chain tool metadata, and cross-chain data. Base and Optimism deployments are planned.
Avalanche C-Chain (43114)
Celo (42220)
Contract Descriptions
- MCPRegistry -- On-chain metadata for all EVMCP tools (names, descriptions, versions). Owner-only writes.
- BatchQuery -- Optimized batch reads via Multicall3. Includes multi-balance, multi-contract-check, and multi-token-balance helpers.
- EventAggregator -- Caches event count summaries per contract. Updated by the admin CLI.
- CrossChainCache -- Stores balance snapshots for cross-chain queries. Updated by the admin CLI.
Environment Variables
| TRANSPORT | No | stdio (default) or http for Streamable HTTP transport |
| HTTP_PORT | No | Port for HTTP transport (default: 3402) |
| X402_ENABLED | No | Enable x402 payment gating on HTTP transport |
| X402_PAYEE_ADDRESS | No** | USDC receive address on Base |
| X402_FACILITATOR_URL | No | x402 facilitator URL (has default) |
*Provide either ALCHEMY_API_KEY or all five individual chain RPC URLs.
**Required when X402_ENABLED=true.
Development
License
MIT
Source: README.md at commit c23fe49
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts