nikicat avatar

EVM Wallet Signer

nikicat/mcp-wallet-signer

Routes blockchain transactions through your actual browser wallet instead of asking for private keys in config files. Exposes MCP tools for EVM chains (MetaMask, Rabby) via EIP-6963 and TRON via TronLink. You get connect_wallet, send_transaction, sign_message, sign_typed_data, plus balance lookups that work without opening a browser. Each signing operation spawns a local HTTP server and opens an approval page where you review the transaction in your wallet extension. Works with Ethereum, Polygon, Arbitrum, Base, and other EVM chains plus TRON mainnet and testnets. Reach for this when you want Claude to interact with smart contracts but need to approve every action yourself.

GitHub stars
1
tools
4
transport
STDIO
env vars
2
last updated
Feb 10, 2026

Tools

4 tools

Public tool metadata for what this MCP can expose to an agent.

connect_walletConnect a wallet, return the address

Connect a wallet, return the address

No parameter schema in public metadata yet.

send_transactionSend value or call a contract, return the tx hash

Send value or call a contract, return the tx hash

No parameter schema in public metadata yet.

sign_message`personal_sign` a message, return the signature

`personal_sign` a message, return the signature

No parameter schema in public metadata yet.

sign_typed_dataSign EIP-712 typed data, return the signature

Sign EIP-712 typed data, return the signature

No parameter schema in public metadata yet.

Sponsors

Configuration

EVM_MCP_PORTdefault: 3847

HTTP server port for the browser approval UI (default: 3847)

EVM_MCP_DEFAULT_CHAINdefault: 1

Default EVM chain ID (default: 1 for Ethereum mainnet)

Readme

mcp-wallet-signer

npm version License: MIT

[!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


View the full README on GitHub

Details

Repository
github.com/nikicat/mcp-wallet-signer
Website
github.com/nikicat/mcp-wallet-signer
Category
Web & Browser Automation
Package
mcp-wallet-signer
Transport
STDIO
Registry
MCP registry, active

Related Web & Browser Automation MCP servers

View all
1allyburns avatarTrazo pilotallyburns/trazo-pilotFly Trazo, a browser game over the real Nazca lines, turn by turn, and post to its AI board.0stars
2boltcreative avatarTab Hammerboltcreative/tab-hammerList, group, move, focus, open, and close browser tabs through the Tab Hammer extension.0stars
3caffeine avatarCaffeinecaffeineCaffeine's MCP server lets you build full-stack apps from inside Claude, ChatGPT, Cursor, or other agents. Send a build prompt, get progress updates, and have y0stars
4clonvodotcom avatarClonvoclonvodotcom/mcpWeb search, scraping, crawling, research, a browser agent, and company and people data.0stars
5clauxel avatarAutobrowserapproval Mcpclauxel/autobrowser-approval-cloud-mcpA paid remote MCP for AI agent browser approval MCP, built to return verdicts, receipts, usage logs,0stars
6drmkdaddy avatarCat Burglardrmkdaddy/cat-burglarStealth browser MCP with three engines, proxy pools, remote CDP, diff observations, and benchmarks.0stars