150,000+ agents registered. Trust scores show their math.Explore →
Explorer/MCP/clawallex/clawallex
REMOTE

Clawallex

clawallex/clawallex

MCP Server for the Clawallex payment API. Pay for anything with USDC — Clawallex converts your stablecoin balance into virtual cards that work at any online checkout.

14 tools available
The Newcomer
Hasn't been around long. Nothing caught our attention, but there isn't much history to go on yet.
Time indexed (2mo)
14toolsRemote/ HTTP2moindexed
100% uptime · 297ms avgChecked May 17, 2026
Quality Score
54/95
Established
Risk Score
0/100
Clean
How is this calculated?
Quality Breakdown
Tenure10.5/20
46 days indexed
Capability18/25
Tools: 6/13 (14 tools)
Description: 5/5
Endpoint: 7/7
Adoption0/25
Use count: 0/20 (0 uses)
Multi-registry: 0/5 (1 registry)
Reliability25/25
Currently live: 10/10
Uptime history: 15/15 100% (8/8 checks)
Security scan: 0 pts in v1.0; ready to weight when coverage improves
Incomplete Data Cap (60)
Usage data is not available for this server. Quality is capped until adoption can be measured.
Risk
0Clean
No signals detected.
The scanner shows
14 tools. Nothing caught our attention.
First indexed Apr 1, 2026
Server Profile
Tools catalogued
14
14 tools available. Full list below.
Hosting
Remote / HTTP
Runs on the internet. No access to your filesystem, SSH keys, or environment variables.
Registry presence
Not verified
Not yet verified by the Official MCP Registry.
Liveness
100%
Based on 45 checks. Average response: 297ms.
Publisher Verification
Not yet verified by the Official MCP Registry.
Endpoint
https://clawallex--clawallex.run.tools
Tools (14)
batch_card_balances
Check balances for multiple cards in one call.
clawallex_pay
Pay for a product or service using USDC. Creates a single-use flash virtual card (card_type=100), deducts from wallet balance, returns card details for checkout. Mode A (mode_code=100, default): wallet balance → flash card. Immediate settlement. Mode B (mode_code=200): for callers with self-custody wallets — signing is performed by the caller. x402 on-chain two-stage flow: Stage 1 (Quote): POST with mode_code=200, chain_code, token_code. The 402 response is EXPECTED — it is a quote, NOT an error. Returns: card_order_id, client_request_id, x402_reference_id, payee_address, asset_address, final_card_amount, issue_fee_amount, fx_fee_amount, fee_amount, payable_amount. Agent signs: construct and sign an EIP-3009 transferWithAuthorization using your own wallet/signing library. EIP-712 domain: name="USDC", version="2", verifyingContract=asset_address from Stage 1. authorization fields: from=your wallet, to=payee_address, value=maxAmountRequired, validAfter/validBefore=unix seconds validity window, nonce=random 32-byte hex (unique per auth). authorization.from MUST equal payer_address submitted in Stage 1. Stage 2 (Settle): POST again with SAME client_request_id + signed x402 data: - payment_payload.network and payment_requirements.network MUST equal chain_code from Stage 1 - payment_requirements.payTo MUST equal payee_address from Stage 1 - payment_requirements.asset MUST equal asset_address from Stage 1 - maxAmountRequired = payable_amount × 10^6 (USDC decimals, e.g. '207.59' → '207590000') - payment_requirements.extra.referenceId MUST equal x402_reference_id from Stage 1 - extra.card_amount = amount, extra.paid_amount = amount + fee_amount If settle rejected, order stays pending_payment — fix params and retry with same client_request_id. Fee: fee_amount = issue_fee_amount + fx_fee_amount. total = amount + fee_amount. Example (Mode A): clawallex_pay({ amount: 50, description: 'OpenAI API credits' })
clawallex_refill
Top up the balance of a subscription (stream) card. Only stream cards (card_type=200) can be refilled. Refill mode follows the card's creation mode. Mode A: deducts from wallet balance. client_request_id is the idempotency key (auto-generated if omitted). Mode B: x402 settle (no 402 challenge stage) — agent constructs and signs the payment independently. Step 1: call get_x402_payee_address(chain_code, token_code) to get payee_address and asset_address. payee_address → payment_requirements.payTo asset_address → payment_requirements.asset (the USDC token contract on the target chain, e.g. BASE USDC) Step 2: sign an EIP-3009 transferWithAuthorization using your wallet/signing library. EIP-712 domain: name="USDC", version="2", verifyingContract=asset_address from Step 1. authorization.from MUST equal payer_address submitted in the request. Step 3: maxAmountRequired = amount × 10^6 (USDC has 6 decimals; refill has no extra fee, e.g. '50.00' → '50000000'). Step 4: submit with x402_reference_id, x402_version, payment_payload, payment_requirements. - payment_payload.network and payment_requirements.network MUST equal chain_code used in Step 1 - payment_requirements.extra.referenceId MUST equal x402_reference_id - x402_reference_id is the idempotency key (not client_request_id) Tip: use get_card_balance first to check current balance. Example: clawallex_refill({ card_id: 'c_123', amount: 50 })
clawallex_subscribe
Set up a reloadable virtual card for recurring/subscription payments. Creates a stream card (card_type=200) that stays active and can be refilled via clawallex_refill. Mode A (mode_code=100, default): wallet balance → stream card. Immediate settlement. Mode B (mode_code=200): for callers with self-custody wallets — signing is performed by the caller. x402 on-chain two-stage flow: Stage 1 (Quote): POST with mode_code=200, chain_code, token_code. The 402 response is EXPECTED — it is a quote, NOT an error. Returns: card_order_id, client_request_id, x402_reference_id, payee_address, asset_address, final_card_amount, issue_fee_amount, monthly_fee_amount, fx_fee_amount, fee_amount, payable_amount. Agent signs: construct and sign an EIP-3009 transferWithAuthorization using your own wallet/signing library. EIP-712 domain: name="USDC", version="2", verifyingContract=asset_address from Stage 1. authorization fields: from=your wallet, to=payee_address, value=maxAmountRequired, validAfter/validBefore=unix seconds validity window, nonce=random 32-byte hex (unique per auth). authorization.from MUST equal payer_address submitted in Stage 1. Stage 2 (Settle): POST again with SAME client_request_id + signed x402 data: - payment_payload.network and payment_requirements.network MUST equal chain_code from Stage 1 - payment_requirements.payTo MUST equal payee_address from Stage 1 - payment_requirements.asset MUST equal asset_address from Stage 1 - maxAmountRequired = payable_amount × 10^6 (USDC decimals, e.g. '207.59' → '207590000') - payment_requirements.extra.referenceId MUST equal x402_reference_id from Stage 1 - extra.card_amount = amount, extra.paid_amount = amount + fee_amount If settle rejected, order stays pending_payment — fix params and retry with same client_request_id. Fee: fee_amount = issue_fee_amount + monthly_fee_amount + fx_fee_amount. total = amount + fee_amount. Example: clawallex_subscribe({ initial_amount: 100, description: 'AWS monthly billing' })
create_card_order
Advanced: create a virtual card with full control over payment mode and card type. Most agents should use clawallex_pay or clawallex_subscribe instead. Mode A (mode_code=100): wallet balance deduction, immediate settlement. Mode B (mode_code=200): for callers with self-custody wallets — signing is performed by the caller. x402 two-stage flow: Stage 1 (Quote): provide chain_code + token_code. The 402 response is EXPECTED (a quote, NOT an error). Returns: payee_address, asset_address, x402_reference_id, fee breakdown, payable_amount. Agent signs: construct and sign an EIP-3009 transferWithAuthorization using your own wallet/signing library. EIP-712 domain: name="USDC", version="2", verifyingContract=asset_address from Stage 1. authorization fields: from=your wallet, to=payee_address, value=maxAmountRequired, validAfter/validBefore=unix seconds validity window, nonce=random 32-byte hex (unique per auth). authorization.from MUST equal payer_address submitted in Stage 1. Stage 2 (Settle): reuse SAME client_request_id + provide x402_version, payment_payload, payment_requirements, extra. - payment_payload.network and payment_requirements.network MUST equal chain_code from Stage 1 - payment_requirements.payTo MUST equal payee_address from Stage 1 - payment_requirements.asset MUST equal asset_address from Stage 1 - payment_requirements.extra.referenceId MUST equal x402_reference_id from Stage 1 - maxAmountRequired = payable_amount × 10^decimals (USDC = 6, e.g. '207.59' → '207590000') - extra.card_amount = amount, extra.paid_amount = amount + fee_amount If settle rejected, order stays pending_payment — retry with same client_request_id. card_type: 100=flash (single-use), 200=stream (reloadable). Fee: flash = issue_fee + fx_fee; stream = issue_fee + monthly_fee + fx_fee.
get_card_balance
Get the current balance and status of a virtual card. Returns available_balance, card_currency, status, and updated_at.
Show all 14 tools ↓
get_card_details
Get full card details including PAN, CVV, expiry, balance, cardholder info, billing address, and risk controls.
get_wallet
Get the wallet details for the current API key. Each API key has exactly one wallet — shared across all agents using the same API key. Returns available_balance, frozen_balance, low_balance_threshold, currency (USD), and status. Use this to check if there is sufficient balance before creating cards (Mode A) or refilling (Mode A).
get_wallet_recharge_addresses
Get the on-chain deposit addresses for a wallet. Send USDC to one of these addresses to top up the wallet balance. If the result is empty, no deposit address has been created yet — ask the user to visit https://app.clawallex.com to create one.
get_x402_payee_address
Get the system receiving address for x402 on-chain payments. When to use: MUST call this before Mode B Refill to obtain payee_address and asset_address. Not needed for Mode B card creation — the 402 quote response already includes both addresses. Returns: payee_address (payment_requirements.payTo), asset_address (payment_requirements.asset = USDC token contract).
list_cards
List virtual cards created by this agent (scoped to the server's client_id). Cards created by other agents using the same API key are not visible. Returns: card_id, mode_code, card_type (flash/stream), status, masked PAN, balance, and expiry.
list_transactions
List card transactions for this agent (scoped to the server's client_id). Transactions from other agents using the same API key are not visible. All filter parameters are optional — omit all to list recent transactions across all cards.
update_card
Update card risk controls: per-transaction limit and MCC whitelist/blacklist. At least one field must be provided.
whoami
Query the current MCP connection status. Returns user_id, api_key_id, and client_id bound to this MCP token.

Is this your server?

Create a free RNWY account to connect your on-chain identity to this server. MCP server claiming is coming; register now and you'll be first in line.

Create your account →
More from clawallex
io.github.Clawallex-Tech/clawallex-mcp
MCP Server for Clawallex payment API - Pay for anything with USDC virtual cards
Similar servers
Press Release
press-release MCP — wraps StupidAPIs (requires X-API-Key)
Scream Void
scream-void MCP — wraps StupidAPIs (requires X-API-Key)
MCP Server for LimeSurvey
Enables interaction with LimeSurvey API to create and manage surveys, questions, question groups, activate surveys, and export responses through standardized MCP endpoints.
io.github.zenml-io/mcp-zenml
MCP server for ZenML - browse stacks, pipelines, runs, artifacts & trigger pipeline runs via API
Linear
Linear MCP — wraps the Linear GraphQL API (OAuth)
HAPI MCP Server
HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants
Indexed from Smithery · Updates nightlyView on Smithery →