EVM Wallet Signer
NPM · MCP-WALLET-SIGNER · SCANNED SEP 21
Route EVM transactions to browser wallets (MetaMask, etc.) for signing via EIP-6963
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 121 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to nikicat/mcp-wallet-signer). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 586 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_transaction" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the EVM Wallet Signer MCP server?
EVM Wallet Signer runs locally as an npm package, launched with npx -y mcp-wallet-signer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-wallet-signer
claude mcp add nikicat-mcp-wallet-signer -- npx -y mcp-wallet-signer
{
"mcpServers": {
"nikicat-mcp-wallet-signer": {
"command": "npx",
"args": [
"-y",
"mcp-wallet-signer"
]
}
}
} {
"servers": {
"nikicat-mcp-wallet-signer": {
"command": "npx",
"args": [
"-y",
"mcp-wallet-signer"
]
}
}
} codex mcp add nikicat-mcp-wallet-signer -- npx -y mcp-wallet-signer
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nikicat-mcp-wallet-signer": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-wallet-signer"
],
"enabled": true
}
}
} openclaw mcp add nikicat-mcp-wallet-signer --command npx --arg -y --arg mcp-wallet-signer
mcp_servers:
nikicat-mcp-wallet-signer:
command: "npx"
args: ["-y", "mcp-wallet-signer"] {
"McpServers": {
"nikicat-mcp-wallet-signer": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-wallet-signer"
]
}
}
} assistant mcp add nikicat-mcp-wallet-signer -t stdio -c npx -a -y mcp-wallet-signer
{
"mcpServers": {
"nikicat-mcp-wallet-signer": {
"command": "npx",
"args": [
"-y",
"mcp-wallet-signer"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/mcp-wallet-signer@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | nikicat/mcp-wallet-signer |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/nikicat/mcp-wallet-signer/.github/workflows/publish.yml@refs/tags/v0.1.3 |
| Rekor log index | 938687908 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3f205842f391ac0120e8c76c72469c2898d8996bd29555efeb29f16ea479a7ef69597ae33589108d28fab88fb1855c3bf97e3d36cc3c7c78cd77c60d6 |
Background: How many MCP packages publish verified provenance →
Dependencies 121 packages
| Packages resolved | 121 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
connect_wallet ~85
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).
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | Chain ID to connect to (default: 1 for Ethereum mainnet) |
No output schema declared.
No examples provided.
get_balance ~58
Get the ETH balance of an address. Does not require browser interaction - reads directly from the blockchain.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address to get balance for (0x...) |
| chainId | number | – | Chain ID (default: 1) |
No output schema declared.
No examples provided.
send_transaction ~186
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).
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | Chain ID (default: 1) |
| data | string | – | Contract call data, hex encoded (optional) |
| gasLimit | string | – | Gas limit (optional, will be estimated if not provided) |
| maxFeePerGas | string | – | Max fee per gas in wei (optional) |
| maxPriorityFeePerGas | string | – | Max priority fee per gas in wei (optional) |
| to | string | yes | Recipient address (0x...) |
| value | string | – | Amount in wei to send (optional for contract calls) |
No output schema declared.
No examples provided.
sign_message ~98
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address to sign with (uses connected address if not specified) |
| chainId | number | – | Chain ID |
| message | string | yes | Message to sign |
No output schema declared.
No examples provided.
sign_typed_data ~159
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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Address to sign with |
| chainId | number | – | Chain ID |
| domain | object | yes | EIP-712 domain (name, version, chainId, verifyingContract, salt) |
| message | object | yes | Message data to sign |
| primaryType | string | yes | Primary type name |
| types | object | yes | Type definitions (e.g., { Person: [{ name: 'name', type: 'string' }] }) |
No output schema declared.
No examples provided.
What is the EVM Wallet Signer MCP server?
EVM Wallet Signer is an MCP server listed in the public MCP registry as io.github.nikicat/mcp-wallet-signer. Route EVM transactions to browser wallets (MetaMask, etc.) for signing via EIP-6963. This page covers its npm package (mcp-wallet-signer).
Is the EVM Wallet Signer MCP server safe to use?
EVM Wallet Signer scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EVM Wallet Signer MCP server expose?
EVM Wallet Signer exposes 5 tools: connect_wallet, send_transaction, sign_message, sign_typed_data, get_balance. Their descriptions and schemas cost roughly 586 tokens of context every time the server is loaded.
Is the EVM Wallet Signer MCP server still maintained?
EVM Wallet Signer is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the EVM Wallet Signer MCP server under?
EVM Wallet Signer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.