send_transaction

4 registry entries were observed exposing a tool named send_transaction — 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 8,470 of 26,658 scannable entries (32%) — 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-signerverified
   trust 85/100 · AMCP serverobserved 2026-06-13 · static extraction
   Route EVM transactions to browser wallets (MetaMask, etc.) for signing via EIP-6963
2. io.github.szhygulin/recon-crypto-mcpverified
   trust 85/100 · AMCP serverobserved 2026-06-13 · static extraction
   Self-custodial crypto portfolio: read EVM DeFi, sign on Ledger via WalletConnect.
3. walletconnect-mcp
   trust 60/100 · BMCP serverobserved 2026-06-24 · static extraction
   Local stdio MCP server that bridges an MCP client to your EVM wallet over WalletConnect — connect by QR, read balances, sign messages and EI
4. io.github.hifriendbot/agentwallet
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Wallet infrastructure for Ai agents. EVM + Solana. x402 payments. No KYC.

All indexed toolsSearch the registry for send_transaction