MCP EVM Signer

Created By
zhangzhongnan928a year ago
MCP server for managing EVM keys and deploying smart contracts via Infura
Overview

What is MCP EVM Signer?

MCP EVM Signer is a Model Context Protocol (MCP) server designed for managing Ethereum private keys and deploying smart contracts using Infura. It allows users to interact with EVM-compatible blockchains through a secure interface.

How to use MCP EVM Signer?

To use MCP EVM Signer, clone the repository, install the dependencies, configure your Infura API key, and integrate it with the Claude for Desktop application. You can then use various commands to manage wallets and deploy contracts.

Key features of MCP EVM Signer?

  • Securely store and manage Ethereum private keys locally
  • Connect to Infura for blockchain interactions
  • Deploy smart contracts from compiled ABIs and bytecode
  • Sign and send transactions
  • View account balances and transaction history
  • Query blockchain data and interact with deployed contracts

Use cases of MCP EVM Signer?

  1. Creating and managing Ethereum wallets
  2. Deploying and interacting with smart contracts
  3. Checking balances and transaction history on Ethereum networks

FAQ from MCP EVM Signer?

  • Is my private key secure?

Yes, private keys are stored locally and can be encrypted with a password.

  • Do I need an Infura account?

Yes, an Infura account with an API key is required to connect to the Ethereum network.

  • Can I use this on test networks?

Yes, it is recommended to use test networks like Sepolia or Goerli for development.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zhangzhongnan928
Star
0
Language
TypeScript
License
-

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