nikicat/mcp-wallet-signer

v0.1.3 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 3mo 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

Summary

AI summary

Added mcpName field and server.json manifest for MCP registry compatibility

Full changelog

Changes

Add mcpName field to package.json for MCP registry compatibility
Add server.json manifest for MCP Server Registry publishing

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.