MCP Wallet Signer allows users to interact with blockchain transactions through their browser wallet, ensuring private keys never leave the browser and requiring user approval for each transaction.
From the registry: Route EVM transactions to browser wallets (MetaMask, etc.) for signing via EIP-6963

Please install the `mcp-wallet-signer` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Browser wallet** — Requires an EIP-6963 compatible browser wallet (MetaMask, Rabby, etc.) open in a browser
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","mcp-wallet-signer"]
Note: Routes every tx to the user's browser wallet via EIP-6963. No private key in config.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.EVM_MCP_PORTHTTP server portEVM_MCP_DEFAULT_CHAINDefault chain IDOpen-source SEC EDGAR toolkit — 11 tools, 7 prompts, every filing type. No API key required.
SEC filing intelligence — insider sentiment, material events, financial ratios, disclosure search.
MCP server for Stripe — global payments API (PaymentIntents, Checkout, Billing, Refunds)