io.github.nikicat/mcp-wallet-signer

MCPattested
v0.1.3io.github.nikicatUnknownUpdated 7mo agonpmGitHub

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

Your private keys never leave your browser. Every transaction requires explicit user approval in your wallet. Most blockchain MCPs require you to paste a private key into a config file — giving the AI agent full, unsupervised access to your funds. MCP Wallet Signer takes a different approach: it routes every transaction to your actual browser wallet — EVM wallets (MetaMask, Rabby, …) via…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2GitHub stars
2Forks
7mo agoLast update
Package
Authorio.github.nikicat
LicenseUnknown
Version0.1.3
Sourcemcp-registry
npmmcp-wallet-signer
GitHubnikicat/mcp-wallet-signer
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 31bb79d
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface20 tools · none privileged
Security scan✓ Cleanv0.6.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

20 tools · none privileged
Statically extracted from the published packagev0.6.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

connect_walletNo description published

This tool published no description. Forge does not invent one.

send_transactionNo description published

This tool published no description. Forge does not invent one.

sign_messageNo description published

This tool published no description. Forge does not invent one.

sign_typed_dataNo description published

This tool published no description. Forge does not invent one.

get_balanceNo description published

This tool published no description. Forge does not invent one.

get_token_balanceNo description published

This tool published no description. Forge does not invent one.

tron_connect_walletNo description published

This tool published no description. Forge does not invent one.

tron_send_transactionNo description published

This tool published no description. Forge does not invent one.

tron_trigger_contractNo description published

This tool published no description. Forge does not invent one.

tron_sign_messageNo description published

This tool published no description. Forge does not invent one.

tron_sign_typed_dataNo description published

This tool published no description. Forge does not invent one.

tron_get_balanceNo description published

This tool published no description. Forge does not invent one.

tron_get_token_balanceNo description published

This tool published no description. Forge does not invent one.

send-ethNo description published

This tool published no description. Forge does not invent one.

amountNo description published

This tool published no description. Forge does not invent one.

addressNo description published

This tool published no description. Forge does not invent one.

chainNo description published

This tool published no description. Forge does not invent one.

check-balanceNo description published

This tool published no description. Forge does not invent one.

sign-messageNo description published

This tool published no description. Forge does not invent one.

messageNo description published

This tool published no description. Forge does not invent one.

0 of 20 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Your private keys never leave your browser. Every transaction requires explicit user approval in your wallet. Most blockchain MCPs require you to paste a private key into a config file — giving the AI agent full, unsupervised access to your funds. MCP Wallet Signer takes a different approach: it routes every transaction to your actual browser wallet — EVM wallets (MetaMask, Rabby, …) via EIP-6963, and TRON via TronLink — so you review and approve each action just like any other dapp…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

19 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in crypto & web3