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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

35 minutes ago