MCP.Market

EVM Wallet Signer MCP server

by nikicat·io.github.nikicat/mcp-wallet-signer·v0.1.3·3 stars
No reviews yet

Route EVM transactions to browser wallets (MetaMask, etc.) for signing via EIP-6963

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

3 stars86 downloads/wk

Reviews

Write one

Nobody has reviewed EVM Wallet Signer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

EVM Wallet Signer tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • connect_wallet

    Connect to a browser wallet and get the wallet address. IMPORTANT: This tool opens a browser window where the user must approve the connection. Tell the user to switch to their browser window to approve. This tool blocks until the user acts or the request times out (5 min).

  • get_balance

    Get the ETH balance of an address. Does not require browser interaction - reads directly from the blockchain.

  • send_transactionwrite action

    Send a transaction (ETH transfer or contract call) via the connected browser wallet. IMPORTANT: This tool opens a browser window where the user must review and approve the transaction. Tell the user to switch to their browser window to approve. This tool blocks until the user acts or the request times out (5 min).

  • sign_message

    Sign an arbitrary message using personal_sign. IMPORTANT: This tool opens a browser window where the user must approve the signature. Tell the user to switch to their browser window to approve. This tool blocks until the user acts or the request times out (5 min).

  • sign_typed_data

    Sign EIP-712 typed data. IMPORTANT: This tool opens a browser window where the user must review and approve the signature. Tell the user to switch to their browser window to approve. This tool blocks until the user acts or the request times out (5 min).

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 10 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How EVM Wallet Signer compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 85% of 866 Scraping and browsing servers
Tools
5
the typical Scraping and browsing server has 6
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 70% of 583 Scraping and browsing servers
Downloads a week
86
more than 52% of 309 Scraping and browsing servers with a package

What its tools let an agent do: 4 read · 1 send or post

Install EVM Wallet Signer in Claude Code, Cursor or VS Code

Runs npx -y mcp-wallet-signer on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-wallet-signer -- npx -y mcp-wallet-signer
Add to Cursor

What the publisher says

From the EVM Wallet Signer repository's README, as published. We do not edit it. Read it on GitHub

mcp-wallet-signer

[!WARNING]

Superseded by browser-web3-signer — the

same browser-wallet signing flow, reimplemented in Rust with a CLI plus Rust/TypeScript/Go

libraries. Everything published from this repo is now a thin compatibility shim over it, so

existing installs keep working; new code should use browser-web3-signer directly.

Your private keys never leave your browser. Every transaction requires explicit approval in your own wallet (MetaMask, Rabby, TronLink, …).

Most blockchain tooling wants a private key in a config file — full, unsupervised access to your funds. These packages route each request to the browser wallet you already use, so you review and approve it like any other dapp interaction.

Packages

All three spawn browser-web3-signer serve, which owns the localhost bridge, the approval page and the browser tab. The binary for your platform is installed as a dependency; nothing else to set up.

MCP server

claude mcp add wallet-signer -- npx -y mcp-wallet-signer

Or, for Claude Desktop / Cursor / Windsurf and any other stdio MCP client:

{
  "mcpServers": {
    "wallet-signer": {
      "command": "npx",
      "args": ["-y", "mcp-wallet-signer"]
    }
  }
}

EVMMCPDEFAULT_CHAIN sets the chain id used when a call omits one (default: 1).

Libraries

import { WalletSigner } from "browser-evm-signer";

const signer = new WalletSigner({ defaultChainId: 8453 });
const { address } = await signer.connectWallet();
const { txHash } = await signer.sendTransaction({ to: "0x…", value: "1000000000000000000" });

What changed in the shims

buildConnectUrl, buildSignUrl, openBrowser — the in-process HTTP bridge they drove no longer exists.

  • Gone: PendingStore, pendingStore, createHttpServer, startTestServer,

does not hand the per-request URL back.

  • approvalUrl is now the bridge's base URL. The bridge opens the approval page itself and

getPort() / DEFAULT_PORT still resolve, for source compatibility.

  • port (the constructor option) is ignored: the bridge binds its own free port.

from the MCP server. Balances never needed a wallet — any RPC-reading MCP server or cast call does them without an approval prompt — and TRON signing is a CLI away. WalletSigner.getBalance and .getTokenBalance are untouched in both libraries.

  • MCP: the balance tools (getbalance, gettoken_balance) and the TRON tools are gone

pointed at ./esm/mod.js while the tarball shipped ./esm/browser-evm-signer/src/mod.js, which took mcp-wallet-signer@0.6.0 down with it (#2).

  • Deprecated on npm and JSR. browser-evm-signer@0.3.0 never worked at all: its exports

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

EVM Wallet Signer: common questions

Is EVM Wallet Signer MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the EVM Wallet Signer safety report
How do I install EVM Wallet Signer?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does EVM Wallet Signer need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is EVM Wallet Signer maintained?
The last commit was 47 days ago (2026-09-18). The latest release is v0.1.3.
What can I use instead of EVM Wallet Signer?
Servers from other publishers that do the same job: GrowBlocks Dev Kit MCP server, SeleniumBase MCP server and Next AI Draw.io MCP server.
How does EVM Wallet Signer compare with other Scraping and browsing MCP servers?
safety score 92/100 (higher than 85% of 866 Scraping and browsing servers); tools 5 (the typical Scraping and browsing server has 6); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to EVM Wallet Signer

Same job from other publishers: the closest match first, then the best rated.

  • GrowBlocks Dev Kit
    Build, play-test with screenshots, and ship three.js browser games on GrowBlocks.
    A
  • SeleniumBase MCP
    Stealthy browser automation, testing, and web-scraping via CDP Mode.
    A
  • Next AI Draw.io
    draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
    A
  • AIHawk
    AI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.
    More from feder-cr →
    A
  • Browser
    MCP server for browser use access
    B