sign_typed_data

2 registry entries were observed exposing a tool named sign_typed_data — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,342 of 40,590 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. io.github.nikicat/mcp-wallet-signerMCPattestedtrust 85/100 · A

   v0.1.3

   ★ 2

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

   ClaudeCursorCopilotGemini

   io.github.nikicatUnknown8mo agonpmGitHub+compareobserved 2026-06-13 · static extraction

   mcp
2. walletconnect-mcpMCPcommunitytrust 60/100 · B

   v0.0.4

   ↓ 389/wk

   Local stdio MCP server that bridges an MCP client to your EVM wallet over WalletConnect — connect by QR, read balances, sign messages and EIP-712 typed data, sign and send transactions. Non-custodial; all signing happens in your wallet.

   ClaudeCursorCopilotGemini

   Wonhee LeeMIT3mo agonpmGitHub+compareobserved 2026-06-24 · static extraction

   mcp

All indexed toolsSearch the registry for sign_typed_data