evm-mcp-server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Read EVM blockchain and send signed token transfers through MCP

What we know

MCP server that provides LLMs with tools for interacting with EVM networks Read EVM blockchain and send signed token transfers through MCP.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-03T16:56:41Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: transfer_native; transfer_erc20; approve_token_spending; write_contract; sign_message. Complete write authority is not verified.
Wallet private key or mnemonic / RPC settings
Sensitive access: Private wallet key, chain balances and transaction data

High-risk on-chain actions include native/ERC20 transfers, allowances, contract writes and signing; default HTTP host 0.0.0.0 in documented server.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

377 repository stars

Stars observed Oct 9, 2026.

Repository total for mcpdotdirect/evm-mcp-server.

All limitations / Review context

Has evm-mcp-server changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

High-risk on-chain actions include native/ERC20 transfers, allowances, contract writes and signing; default HTTP host 0.0.0.0 in documented server.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Wallet private key or mnemonic / RPC settings
Private wallet key, chain balances and transaction data
Reviewed write actions: transfer_native; transfer_erc20; approve_token_spending; write_contract; sign_message
Sensitive access: Private wallet key, chain balances and transaction data
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-03T16:56:41Z

Technical identity

github.com/mcpdotdirect/evm-mcp-server

Exact implementation source: https://github.com/mcpdotdirect/evm-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: mcpdotdirect/evm-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
mcpdotdirect/evm-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

generic

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
EVM MCP Server can read blockchains without wallet secrets; wallet keys enable financial write actions.
mcp stdio launcher or diagnostic · Publisher instructions
npx @mcpdotdirect/evm-mcp-server
Configure / authenticate
Publisher instructions
EVM MCP includes private-key or mnemonic wallet capability and token transfers. Never place wallet secrets in public config, and do not run trading, transfer, approval or signing tools as setup checks.
Check connection
Suggested check
Use keyless read-only chain metadata or block lookups on a test RPC.
Remove / uninstall / revoke
MCP100 setup guide
Only for matching registered name; stop the local EVM MCP process. No effect on wallet or token balances.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
claude mcp remove evm-mcp

Official Documentation & Sources

What it does

MCP server that provides LLMs with tools for interacting with EVM networks Read EVM blockchain and send signed token transfers through MCP.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Read EVM blockchain and send signed token transfers through MCP

Representative uses

Read EVM balances and transactions
Inspect token allowances and smart contracts
Submit signed transactions only with explicit control
Read EVM blockchain and send signed token transfers through MCP

Limitations

High-risk on-chain actions include native/ERC20 transfers, allowances, contract writes and signing; default HTTP host 0.0.0.0 in documented server.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Wallet private key or mnemonic / RPC settings
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Private wallet key, chain balances and transaction data
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: High-risk on-chain actions include native/ERC20 transfers, allowances, contract writes and signing; default HTTP host 0.0.0.0 in documented server.

Access scope and cautions

Write actions: Not verified transfer_native transfer_erc20 approve_token_spending write_contract sign_message
Sensitive access: Private wallet key, chain balances and transaction data
Risk level: critical
Security notes: High-risk on-chain actions include native/ERC20 transfers, allowances, contract writes and signing; default HTTP host 0.0.0.0 in documented server.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read EVM balances and transactions; Inspect token allowances and smart contracts; Submit signed transactions only with explicit control; Read EVM blockchain and send signed token transfers through MCP.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Default documented host 0.0.0.0, port 3001; use isolated wallet and keep private key/mnemonic out of configs and git. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Wallet private key or mnemonic / RPC settings

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: transfer_native; transfer_erc20; approve_token_spending; write_contract; sign_message. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Private wallet key, chain balances and transaction data Recorded sensitive-access context: Private wallet key, chain balances and transaction data.

What limitations and risks should I check before use?

High-risk on-chain actions include native/ERC20 transfers, allowances, contract writes and signing; default HTTP host 0.0.0.0 in documented server. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.