nikicat/mcp-wallet-signer

v0.3.0 Feature

This release adds 1 notable feature for engineering teams evaluating rollout.

Published 2mo MCP Browser & Automation

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-agent blockchain eip-6963 ethereum mcp metamask

+5 more

model-context-protocol non-custodial typescript wallet web3

Affected surfaces

auth

Summary

AI summary

Added optional address parameter to connectWallet() for validation.

Full changelog

New Feature

Required wallet address for connectWallet() — New optional address parameter flows from the MCP connect_wallet tool through the HTTP server to the browser UI. When set, the UI validates the connected address and shows a "Wrong Address" state on mismatch, with auto-detection via accountsChanged events when the user switches accounts.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track nikicat/mcp-wallet-signer

Get notified when new releases ship.

About nikicat/mcp-wallet-signer

Non-custodial EVM wallet MCP — routes transactions to browser wallets (MetaMask, etc.) for signing. Private keys never leave the browser; every action requires explicit user approval via EIP-6963.

All releases →

Related context

Related tools

Earlier breaking changes

[email protected] Migrates from browser-tron-signer v0.3.x to mcp-wallet-signer v0.6.0.
[email protected] Removes support for browser-tron-signer v0.3.x APIs.
[email protected] API schema changed to a maximalist format, breaking compatibility.
[email protected] MCP wallet signer API schema is now maximalist and incompatible with previous versions.
[email protected] Removes deprecated `legacySigner` API, requiring updates to existing integrations.