EVM MCP Server

Name: EVM MCP Server
Author: zhangzhongnan928

@zhangzhongnan928

About EVM MCP Server

A MCP (Master Control Program) server for interacting with EVM smart contracts with a web interface for transaction confirmations

#evm #smart-contracts #web-interface

Basic information

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is EVM MCP Server?

EVM MCP Server is an MCP (Model Context Protocol) server that enables interaction with EVM smart contracts through both read and write operations. It pairs a backend MCP server with a web DApp for wallet-based transaction confirmation, making it suitable for developers and users who need secure, multi-chain EVM interaction.

How to use EVM MCP Server?

Setup and installation details are provided in individual README files within the /server and /client directories. The server handles read operations via API keys, while write operations require a user’s wallet signature through the web DApp interface.

Key features of EVM MCP Server

Read operations through MCP server using API keys
Write operations requiring wallet signature via Web DApp
Support for multiple EVM chains
Secure API key storage
Transaction monitoring

Use cases of EVM MCP Server

Querying on-chain data from EVM smart contracts
Executing contract transactions with user‑controlled wallet signing
Managing interactions across different EVM‑compatible blockchains
Building DApps that need a secure transaction confirmation layer

FAQ from EVM MCP Server

How does EVM MCP Server differ from a standard RPC provider?

EVM MCP Server separates read operations (handled by the MCP server with API keys) from write operations (requiring a wallet signature via the web DApp), giving users more control over transaction authorization.

What dependencies or runtime are required?

The project uses a Node.js‑based MCP server and a frontend web DApp. Specific runtime and dependency details are found in the /server and /client README files.

Where are transaction data and API keys stored?

API keys are stored securely on the MCP server. Transactions are initiated from the user’s wallet via the web DApp; on‑chain data resides on the respective EVM blockchain.

What transports and authentication methods are supported?

The MCP server likely uses standard MCP transport (e.g., stdio or HTTP). Read operations authenticate via API keys; write operations authenticate through the user’s wallet signature.

Are there any known limits?

The README does not mention specific limits, but the server supports multiple EVM chains and monitors transactions, implying it can handle common use cases for EVM interaction.