This release keeps dependencies and maintenance posture current for teams operating this tool.
✓ No known CVEs patched in this version
Topics
+5 more
ReleasePort's take
Light signalVersion 0.2.0 of browser-evm-signer introduces major API changes.
Why it matters: Plan a migration for any code using the API surface before upgrading to 0.2.0; breaking changes are indicated by the version bump from 0.1.13.
Summary
Routine maintenance release for nikicat/mcp-wallet-signer.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Breaking | High |
Version bumped from 0.1.13 to 0.2.0, indicating potential breaking changes. Version bumped from 0.1.13 to 0.2.0, indicating potential breaking changes. Source: granite4.1:30b@2026-05-21-audit Confidence: low |
— |
| Breaking | Medium |
Major API changes introduced in version 0.2.0. Major API changes introduced in version 0.2.0. Source: llm_adapter@2026-05-21 Confidence: low |
— |
Full changelog
Full Changelog: https://github.com/nikicat/mcp-wallet-signer/compare/[email protected]@0.2.0
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
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.
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.
Beta — feedback welcome: [email protected]