@sinco-lab/evm-mcp-server

Name: @sinco-lab/evm-mcp-server
Author: sinco-lab

@sinco-lab

代码仓库

关于 @sinco-lab/evm-mcp-server

An EVM interaction service based on Model Context Protocol (MCP)

基本信息

分类

其他

运行时

node

传输方式

stdio

发布者

sinco-lab

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "evm-mcp-server-sinco-lab": {
      "command": "node",
      "args": [
        "build/evm.js"
      ]
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is @sinco-lab/evm-mcp-server?

An EVM interaction service gateway based on Model Context Protocol (MCP) and Viem, enabling AI agents or services to securely interact with a configured EVM-compatible blockchain.

How to use @sinco-lab/evm-mcp-server?

Install dependencies with pnpm install, build with pnpm run build, then configure environment variables (WALLET_PRIVATE_KEY, RPC_PROVIDER_URL) in a .env file or directly in a client’s MCP server config. Run the server using node build/evm.js or configure clients like Cursor or Claude Desktop to launch it automatically.

Key features of @sinco-lab/evm-mcp-server

Exposes EVM functionalities as standard MCP tools.
Uses the modern Viem library for reliable EVM interactions.
Connects to any EVM-compatible chain via configurable RPC URL.
Provides tools for balances, transfers, token operations, and message signing.
Developed entirely in TypeScript for type safety and maintainability.

Use cases of @sinco-lab/evm-mcp-server

AI agents performing on-chain transactions like token transfers.
Querying wallet balances and token allowances programmatically.
Signing messages or approving token spenders via AI-driven workflows.
Automating approval and token transfer operations in dApp bots.
Enabling chatbots or virtual assistants to interact with EVM blockchains.

FAQ from @sinco-lab/evm-mcp-server

What is the purpose of @sinco-lab/evm-mcp-server?

It acts as a gateway for AI agents or MCP clients to securely interact with EVM-compatible blockchains, exposing blockchain operations as standardized MCP tools.

What dependencies are required to run the server?

Node.js version 18.0.0 or higher and the pnpm package manager are required.

How are blockchain credentials configured?

The server uses environment variables WALLET_PRIVATE_KEY (the wallet’s private key) and RPC_PROVIDER_URL (the JSON‑RPC endpoint). These can be placed in a .env file or directly in the MCP client’s configuration file.

Which EVM operations does the server support?

The server exposes tools for checking balances, sending native tokens, transferring ERC20 tokens, signing messages, getting token allowances, approving/revoking allowances, and more – a full list is available in the README.

How should private keys be managed for security?

It is strongly recommended to use a dedicated wallet for testing. Never commit private keys to version control, and avoid placing them directly in configuration files (e.g., .cursor/mcp.json) for high‑value environments.