📌Overview

Purpose: To provide a Model Context Protocol (MCP) server that enables AI models to interact with Ethereum blockchain data through standardized JSON-RPC calls.

Overview: The Ethereum RPC MPC server acts as a bridge between AI assistants and EVM blockchains, facilitating seamless access to on-chain data and functionalities using the Model Context Protocol, specifically designed for enhanced interactions with Ethereum blockchain data.

Key Features:

Supports All JSON-RPC Calls: Enables AI models to perform any Ethereum-related blockchain query or operation using standardized JSON-RPC interfaces, enhancing the versatility of blockchain interactions.
Zircuit Specific Methods: Integrates specialized RPC methods for Zircuit that provide additional functionalities like monitoring transaction quarantine status, allowing for more tailored blockchain management.

Ethereum RPC MPC Server

A TypeScript MCP server that leverages the MCP SDK to support all Ethereum JSON-RPC calls, enabling AI models to interact with blockchain data.

Overview

This project provides a Model Context Protocol (MCP) server that allows AI assistants like Cursor or Claude (or any MCP Client implementation) to interact with Ethereum blockchain data through standardized JSON-RPC interfaces. It acts as a bridge between AI models and EVM blockchains, enabling seamless access to on-chain data and functionality.

Installation

# Clone the repository
git clone git@github.com:Phillip-Kemper/ethereum-rpc-mpc.git
cd ethereum-rpc-mpc

# Install dependencies
yarn install

# Build the project
yarn build

# Start Inspector with default Ethereum RPC (you can change in the inspector settings)
yarn inspector

Usage

Using with Cursor

To use this MPC server with Cursor:

In Cursor, go to Settings > Cursor Settings > MCP
Add a new MCP server with the following configuration:
- Name: Ethereum RPC
- Type: Command
- Command: npx -y ethereum-rpc-mpc https://eth.llamarpc.com Ethereum or
- Command: node /path/to/ethereum-rpc-mpc/dist/server/index.js https://eth.llamarpc.com Ethereum

Analytics

You can enable analytics using MCP Analytics Middleware to get an overview of the number of requests, duration, and error reporting for all your tools and resources. To enable it, pass the --analytics flag and provide a path for the Sqlite database file.

Example command:

npx -y ethereum-rpc-mpc https://eth.llamarpc.com Ethereum --analytics --db-path /path/to/analytics.db

Starting the Server

Start the server by providing an Ethereum RPC URL and an optional chain name:

yarn start [RPC_URL] [CHAIN_NAME]

# Or using npx (without installing)
npx -y ethereum-rpc-mpc [RPC_URL] [CHAIN_NAME]

If no RPC URL is provided, it defaults to https://eth.llamarpc.com.

Examples:

# Connect to Ethereum mainnet
yarn start https://eth.llamarpc.com Ethereum

# Connect to Zircuit
yarn start https://mainnet.zircuit.com Zircuit

Examples

Examples of interacting with the Ethereum RPC MPC server using Claude:

Getting the current block number:
```
What's the current block number?
```

Checking an address balance:

What's the ETH balance of 0x742d35Cc6634C0532925a3b844Bc454e4438f44e?

Getting contract information:

Is 0x6B175474E89094C44Da98b954EedeAC495271d0F a smart contract? If yes, what kind of contract is it?

Retrieving transaction details:

Can you show me the details of transaction 0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060?

Zircuit SLS (Sequencer Level Security) Methods

This server supports Zircuit-specific RPC methods, automatically enabled when connecting to a Zircuit endpoint (Chain ID: 48900). These include:

zirc_isQuarantined: Check if a specific transaction is quarantined
zirc_getQuarantined: Query all quarantined transactions with optional address filtering

These methods are useful for monitoring transaction quarantine status.

Future Steps

Support Indexed API Access: Extend functionality to include indexed blockchain data APIs for efficient querying of historical data and complex analytics.
Multi Chain, Multi RPC Support: Enable connections to multiple chains and RPC endpoints simultaneously to access data across different blockchains in a single session.
Client Implementation: Develop a client-side implementation to facilitate easier interaction with this MCP server from various applications.
Server Analytics: Add analytics to track usage patterns, popular RPC methods, and performance metrics for optimization and insights.

License

MIT