Ethereum RPC MPC Server

Created By
Phillip-Kempera year ago
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

What is Ethereum RPC MPC Server?

Ethereum RPC MPC Server is a TypeScript Model Context Protocol (MCP) server that enables AI models to interact with Ethereum blockchain data through standardized JSON-RPC calls.

How to use Ethereum RPC MPC Server?

To use the server, clone the repository, install dependencies, and start the server with an Ethereum RPC URL. You can also configure it with AI assistants like Cursor or Claude.

Key features of Ethereum RPC MPC Server?

  • Supports all Ethereum JSON-RPC calls.
  • Acts as a bridge between AI models and EVM blockchains.
  • Includes special support for Zircuit-specific RPC methods.

Use cases of Ethereum RPC MPC Server?

  1. Querying the current block number on Ethereum.
  2. Checking the ETH balance of a specific address.
  3. Retrieving transaction details and contract information.

FAQ from Ethereum RPC MPC Server?

  • Can I use this server with any AI model?

Yes! It is designed to work with any MCP Client implementation.

  • Is there support for multiple chains?

Future versions will include support for multiple chains and RPC endpoints.

  • What is the license for this project?

The project is licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Phillip-Kemper
Star
6
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago