home / mcp / ethereum rpc mcp server
Provides an Ethereum RPC MCP server to query on-chain data and metadata via standardized MCP calls, with optional analytics and Zircuit support.
Configuration
View docs{
"mcpServers": {
"phillip-kemper-ethereum-rpc-mpc": {
"command": "npx",
"args": [
"-y",
"ethereum-rpc-mpc",
"https://eth.llamarpc.com",
"Ethereum"
]
}
}
}You can run an Ethereum RPC MCP Server locally or via a remote execution path to let AI models access Ethereum blockchain data through standard JSON-RPC calls. This server bridges AI assistants with EVM-compatible networks, enabling practical queries like block numbers, balances, contract info, and transaction details, while also offering specialized Zircuit security checks when connected to a Zircuit endpoint.
You use this MCP server by running it as an MCP endpoint and then connecting your MCP client to it. Start it with a specific Ethereum RPC URL and chain name, and your client can issue standard Ethereum JSON-RPC calls through the MCP protocol. You can also enable analytics to track usage and performance. If you connect to a Zircuit endpoint, you gain access to additional quarantine-related RPC methods.
Prerequisites you need installed on your machine before running the server are Node.js and a package manager (npm, yarn, or npx). Ensure you have network access to fetch dependencies.
# Clone the server repository
git clone [email protected]:Phillip-Kemper/ethereum-rpc-mpc.git
cd ethereum-rpc-mpc
# Install dependencies
yarn install
# Build the project
yarn build
# Start the Inspector with default Ethereum RPC (adjust settings as needed)
yarn inspectorAnalytics can be enabled to gain insights about the number of requests, request durations, and error reporting across tools. Use the analytics flag together with a database path when starting the server.
yarn start https://eth.llamarpc.com Ethereum
# Optional analytics example (if analytics support is configured)
# npx -y ethereum-rpc-mpc https://eth.llamarpc.com Ethereum --analytics --db-path /path/to/analytics.dbThis server supports standard Ethereum RPC interactions and includes specialized methods for Zircuit when connected to a Zircuit endpoint (Chain ID 48900). The Zircuit methods include checks for quarantined transactions and filtering by address.
Query the current Ethereum block number from the connected RPC endpoint.
Fetch the ETH balance for a given address on the connected network.
Determine whether an address is a smart contract and identify its type if possible.
Retrieve detailed information for a specific transaction by hash.
Check if a specific transaction is quarantined when connected to a Zircuit endpoint.
Query all quarantined transactions with optional address filtering on a Zircuit endpoint.