MCP.so
Sign In
Servers

Clawallex MCP Server

@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.

Overview

What is Clawallex MCP Server?

An MCP server for the Clawallex payment API. It lets you pay for anything online with USDC by converting stablecoin balances into virtual cards that work at any checkout.

How to use Clawallex MCP Server?

Install globally via npm install -g @clawallex/mcp-server or run directly with npx. Obtain API credentials from Clawallex, then configure your AI client (Claude Desktop, Claude Code, Codex CLI, Gemini CLI, OpenCode) with your API key and secret. Run the clawallex_setup tool once to verify the connection and bind a client identity.

Key features of Clawallex MCP Server

  • One-time payments and recurring subscriptions via virtual cards
  • Wallet balance and USDC deposit address queries
  • Encrypted card details (PAN/CVV) with client-side decryption
  • Client ID scoping for agent data isolation
  • Multiple transport modes: stdio, SSE, Streamable HTTP

Use cases of Clawallex MCP Server

  • Pay for online services (e.g., OpenAI credits) with a single-use virtual card
  • Set up reloadable cards for recurring monthly subscriptions (e.g., AWS)
  • Check wallet USDC balance and recharge from on-chain addresses
  • Manage and monitor virtual cards, transactions, and risk controls

FAQ from Clawallex MCP Server

What is a client ID and why is it needed?

A client ID is a stable, agent-specific identity separate from your API key. It scopes card and transaction data per agent, and once bound to an API key it cannot be changed (Trust On First Use). Losing it means losing access to all cards created under it.

How are card details (PAN/CVV) protected?

get_card_details returns encrypted sensitive data. You must call decrypt_card_data using a key derived from your API secret via HKDF-SHA256 and AES-256-GCM. Decrypted data must never be displayed to the user.

What transport modes are supported?

The server supports stdio (default for local agents), sse, and http (Streamable HTTP for MCP SDK 1.0+). Use the --transport flag to select and --port to set the HTTP port.

What are the runtime requirements?

Node.js version 22 or later is required.

How is data isolated between agents?

The wallet balance is shared across all agents using the same API key. Cards, transactions, and other payment data are scoped by client_id — each agent only sees data it created.

Tags

More from Other