官方说明7 个来源MCP 服务8 天前
nikicat/mcp-wallet-signer
📇 🏠 - Non-custodial EVM wallet that routes transactions to browser wallets like MetaMask for signing, with…
在 GitHub 查看 ↗直链 · 无中转页
官方说明📇 🏠 - Non-custodial EVM wallet that routes transactions to browser wallets like MetaMask for signing, with explicit user approval for every action via EIP-6963.
配置模板（请按你的客户端调整）
claude mcp add mcp-wallet-signer -- npx -y mcp-wallet-signer
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 2 ★ · nikicat/mcp-wallet-signer · 取自该仓库的 GitHub 页面 · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
- 评分构成
- 综合分 703 · 2 ★ · 7 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
nikicat/mcp-wallet-signer；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
mcp-wallet-signer
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
> [!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
| Package | What it is now |
|---------|----------------|
| mcp-wallet-signer | MCP stdio server: four signing tools over browser-web3-signer |
| browser-evm-signer | The old WalletSigner EVM library API, re-backed by the Rust bridge |
| browser-tron-signer | The same for TRON (TronLink, TRC-20, contract deploys) |
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
Or, for Claude Desktop / Cursor / Windsurf and any other stdio MCP client:
| Tool | Description |
|------|-------------|
| connect_wallet | Connect a wallet, return the address |
| send_transaction | Send value or call a contract, return the tx hash |
| sign_message | personal_sign a message, return the signature |
| sign_typed_data | Sign EIP-712 typed data, return the signature |
EVM_MCP_DEFAULT_CHAIN sets the chain id used when a call omits one (default: 1).
Libraries
What changed in the shims
- **Gone:** PendingStore, pendingStore, createHttpServer, startTestServer,
buildConnectUrl, buildSignUrl, openBrowser — the in-process HTTP bridge they drove no
longer exists.
- **approvalUrl** is now the bridge's base URL. The bridge opens the approval page itself and
does not hand the per-request URL back.
- **port** (the constructor option) is ignored: the bridge binds its own free port.
getPort() / DEFAULT_PORT still resolve, for source compatibility.
- **MCP:** the balance tools (get_balance, get_token_balance) and the TRON tools are gone
from the MCP server. Balances never needed a wallet — any RPC-reading MCP server or cast call
> **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
| Package | What it is now |
|---------|----------------|
| mcp-wallet-signer | MCP stdio server: four signing tools over browser-web3-signer |
| browser-evm-signer | The old WalletSigner EVM library API, re-backed by the Rust bridge |
| browser-tron-signer | The same for TRON (TronLink, TRC-20, contract deploys) |
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
Or, for Claude Desktop / Cursor / Windsurf and any other stdio MCP client:
| Tool | Description |
|------|-------------|
| connect_wallet | Connect a wallet, return the address |
| send_transaction | Send value or call a contract, return the tx hash |
| sign_message | personal_sign a message, return the signature |
| sign_typed_data | Sign EIP-712 typed data, return the signature |
EVM_MCP_DEFAULT_CHAIN sets the chain id used when a call omits one (default: 1).
Libraries
What changed in the shims
- **Gone:** PendingStore, pendingStore, createHttpServer, startTestServer,
buildConnectUrl, buildSignUrl, openBrowser — the in-process HTTP bridge they drove no
longer exists.
- **approvalUrl** is now the bridge's base URL. The bridge opens the approval page itself and
does not hand the per-request URL back.
- **port** (the constructor option) is ignored: the bridge binds its own free port.
getPort() / DEFAULT_PORT still resolve, for source compatibility.
- **MCP:** the balance tools (get_balance, get_token_balance) and the TRON tools are gone
from the MCP server. Balances never needed a wallet — any RPC-reading MCP server or cast call
- 来源
- awesome · https://github.com/nikicat/mcp-wallet-signer
- 按领域浏览
- MCP 服务
- Traction
- 2 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。