Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EVM Wallet Signer

NPM · MCP-WALLET-SIGNER

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

Available components

−4 this week 83 Trust /100

Last scanned (14 hours ago)

Scores higher than 76% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency90
  • 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
  • Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
  • 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 Management70
  • Stability observed for 21 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
Changelog

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.

  • 4 Nov 26 −4
    • Stability: pass → 0.67 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 21 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.80 → pass security
  • 16 Oct 26 −2
    • Stability: pass → 0.80 functional
Diagnostics

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 5 Nov 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 SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:3f205842f391ac0120e8c76c72469c2898d8996bd29555efeb29f16ea479a7ef69597ae33589108d28fab88fb1855c3bf97e3d36cc3c7c78cd77c60d6

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 119 packages
Packages resolved 119
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~586 tokens

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 →

Tool Tokens
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).

NameTypeReqDescription
chainIdnumber–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.

NameTypeReqDescription
addressstringyesAddress to get balance for (0x...)
chainIdnumber–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).

NameTypeReqDescription
chainIdnumber–Chain ID (default: 1)
datastring–Contract call data, hex encoded (optional)
gasLimitstring–Gas limit (optional, will be estimated if not provided)
maxFeePerGasstring–Max fee per gas in wei (optional)
maxPriorityFeePerGasstring–Max priority fee per gas in wei (optional)
tostringyesRecipient address (0x...)
valuestring–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).

NameTypeReqDescription
addressstring–Address to sign with (uses connected address if not specified)
chainIdnumber–Chain ID
messagestringyesMessage 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).

NameTypeReqDescription
addressstring–Address to sign with
chainIdnumber–Chain ID
domainobjectyesEIP-712 domain (name, version, chainId, verifyingContract, salt)
messageobjectyesMessage data to sign
primaryTypestringyesPrimary type name
typesobjectyesType definitions (e.g., { Person: [{ name: 'name', type: 'string' }] })

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add nikicat-mcp-wallet-signer -- npx -y mcp-wallet-signer
Common questions

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 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 5 November 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.