Wahlet
Related Servers
Alternatives to Wahlet
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceEnables AI agents to autonomously make policy-controlled payments for APIs and tools via Bitcoin Lightning (L402) and Base USDC (x402), including paying paywalled endpoints, checking balances, and reviewing transactions.321 npm1MIT- AlicenseBqualityBmaintenanceProvides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.401,180 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to check balances and send transactions across multiple blockchains with automatic spending limit protection and policy enforcement.3MIT

IronWallet MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely manage a non-custodial wallet with locally encrypted seed phrases, supporting balance checks, local signing, token transfers, swaps, and interactions across 10+ blockchain networks.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to check their wallet address and USDC balance, preview the cost of an x402 call, and pay for API requests in USDC on Base without an account or API key. Spend caps, allow-lists and blocked contracts are enforced in code before anything is signed, so a prompt injection cannot bypass them.MIT
- AlicenseBqualityDmaintenanceProvides AI agents with a complete payments toolkit on the Pharos Atlantic Testnet, including balance checks, token transfers, conditional payments, batch sends, transaction history, gas estimation, and x402 protocol support.20MIT
TDQS
Scored across 7 tools
Most tools are cleanly separated: balance reads, WBT vs USDT transfers, spending state, and funding addresses each occupy a distinct purpose. The one soft boundary is between 'pay' (sign an x402 USDT challenge only, no settlement) and 'x402_fetch' (full 402-handle-sign-settle flow); the descriptions do disambiguate them, but an agent could plausibly reach for the wrong one first.
Almost everything is snake_case with a clear verb_noun shape (check_balance, transfer_wbt, transfer_usdt, request_funding), and the transfer_* pair is a nice symmetric pattern. Deviations exist: bare 'pay' and the protocol-prefixed 'x402_fetch', plus noun-only 'spending_report', keep it from being fully predictable.
Seven tools is well matched to a wallet/payments agent: one per asset transfer, one per read surface, one per payment path, plus a funding helper. Nothing looks like filler and nothing essential is obviously crowded out.
The lifecycle is largely covered: read balances, move both assets, inspect limits/commitments/history, pay via x402, and bootstrap with a faucet. The gap is spend-limit and approval management (limits are described as owner-defined but no tool sets or amends them), and there is no standalone per-operation status lookup beyond the history in spending_report.