Clawallex MCP Server
Related Servers
Alternatives to Clawallex MCP Server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityDmaintenanceEnables AI agents to manage and use prepaid virtual Visa cards with hard budget limits for secure online transactions. It provides tools for creating cards, checking balances, and retrieving payment credentials with human-in-the-loop approvals.1-
- AlicenseBqualityDmaintenanceConnects AI agents to payment processors (Lithic, Stripe, PayPal) for automated shopping with single-use virtual cards and transaction management.93 npmApache 2.0
- AlicenseBqualityDmaintenancePayment & Transaction Tools that allow AI agents to send, receive, and request payments1117 npm2Apache 2.0
- AlicenseAqualityFmaintenanceEnables AI agents to access paid tools like crypto prices, weather, translation, and web intelligence via per-request USDC payments on Base, with no API keys or subscriptions.1524 npmMIT
- AlicenseAqualityBmaintenanceProvides pay-per-use tools for AI agents like web screenshots and crypto intelligence using automatic USDC micropayments on the Base network. It simplifies access to premium APIs by handling blockchain transactions automatically when a payment is required.1212 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to make payments by securely storing encrypted card details and enforcing user-defined policies, allowing agents to fill checkout forms on any site.15 npmMIT
TDQS
Scored across 18 tools
Several tools have overlapping purposes, such as clawallex_pay/create_card_order (both create cards) and clawallex_refill/refill_card (both refill cards). However, the descriptions clearly distinguish them as 'simple' vs 'advanced' workflows, which helps agents select appropriately.
Most tools use snake_case with verb_noun patterns (e.g., get_card_balance, create_card_order), but four tools use a clawallex_ prefix (clawallex_pay, clawallex_refill, etc.) while their advanced counterparts do not (create_card_order, refill_card). Additionally, bootstrap and whoami break the verb_noun convention.
With 18 tools, the set is slightly heavy but reasonable for the complex domain covering wallet management, flash/stream card lifecycles, x402 on-chain payments, and risk controls. The count reflects necessary separation between Mode A (wallet) and Mode B (self-custody) flows, though the convenience/advanced tool pairs add some bloat.
The surface covers the full card lifecycle: creation (flash and stream), retrieval, balance checks, refilling, transaction history, and risk control updates. Minor gaps exist: there is no tool to cancel/close a card or delete/archive it, forcing agents to rely on expiration or MCC blocking to stop usage.