
Clawallex Mcp
io.github.Clawallex-TechPublished by GitHub account Clawallex-Techv1.0.9Updated Oct 24, 2026
MCP Server for Clawallex payment API - Pay for anything with USDC virtual cards
Overview
Clawallex MCP server lets an AI assistant create and manage USDC-funded virtual payment cards and use them at online checkouts.
- What you can do
- Set up and bind the agent identity, and check wallet balance and USDC deposit addresses, plus list cards and transactions with balances and risk controls (transaction limits, allowed and blocked merchant category codes). Create one-time virtual cards for a payment, or reloadable cards for subscriptions, and refill them. Retrieve card details and decrypt the card number and CVV for checkout. Advanced on-chain x402 tools create card orders and refill stream cards with custom idempotency keys.
- When to use it
- Use it when you want an assistant to pay for online services or subscriptions from a USDC balance through virtual cards, for example buying API credits or setting up recurring billing, and you are comfortable letting it handle card data.
- Requirements
- Local Node.js 22 or newer, run via npx or a global npm install. A Clawallex account with an API key pair, supplied as CLAWALLEX_API_KEY and CLAWALLEX_API_SECRET (or CLI flags). Network access to the Clawallex API; optional base URL, client ID and transport settings.
Installation
In SourceWeft
- Open Clawallex Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@clawallex/mcp-server
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.
Quick Start
1. Install
Or use directly via npx (no install needed).
2. Get API Credentials
Sign up at Clawallex and create an API Key pair (api_key + api_secret).
3. Configure Your AI Client
Choose your client and add the configuration:
Claude Desktop
Add to your claude_desktop_config.json:
Claude Code
Codex CLI
Add to your ~/.codex/config.toml or .codex/config.toml:
Gemini CLI
Add to your ~/.gemini/settings.json:
OpenCode
Add to your opencode.json:
4. Initialize Connection
After configuring, tell your AI agent:
"Run clawallex_setup to check the connection"
clawallex_setup verifies your API Key and automatically binds a client_id for data isolation. You only need to do this once.
5. Start Using
One-time payment:
"Pay $50 for OpenAI API credits"
Agent calls clawallex_pay → creates virtual card → get_card_details → decrypt_card_data → fills checkout.
Subscription:
"Set up a $100 card for AWS monthly billing"
Agent calls clawallex_subscribe → creates reloadable card → clawallex_refill when balance is low.
6. Smoke Test
Verify everything works:
Typical Flows
Payment Flow (Mode A — Wallet Balance)
Subscription Flow
Tools
High-Level (Recommended)
Identity & Binding
Wallet & Query
Advanced (x402 On-Chain)
CLI Options
CLI arguments take precedence over environment variables. You can mix both — e.g. set credentials via env vars and override --transport via CLI.
Requirements
- Node.js >= 22
Client ID
client_id is the agent's stable identity, separate from the API Key. It is sent as X-Client-Id on every /payment/* request.
Key concept: An agent can have multiple API Keys (for rotation/revocation), but the client_id never changes. When switching to a new API Key, keep using the same client_id — the new key auto-binds on first request.
Data isolation:
- Wallet: user-level, shared — all agents using the same API key see the same wallet balance
- Cards & Transactions:
client_id-scoped — each agent only sees data it created
Binding rules:
clawallex_setupautomatically callsbootstrapto bindclient_idon first use- Once bound, the
client_idcannot be changed for that API Key (TOFU — Trust On First Use) - Losing the
client_id= losing access to all cards created under it
Resolution order at startup:
--client-id <value>CLI argument (must be >= 36 characters)~/.clawallex-mcp/client_ids.jsonlocal file (from a previous run)- Auto-generate UUID v4 and save locally
Recommendation: Always pass --client-id explicitly in production to avoid relying on the local file.
Transport Modes
stdio (default — local agent / Claude Desktop)
SSE (remote agent, compatible with older MCP clients)
Agent connects to: http://localhost:18080/sse
Streamable HTTP (MCP SDK 1.0+ recommended)
Agent connects to: http://localhost:18080/mcp
Local Development
Security
Authentication
Every API request is signed with HMAC-SHA256:
Signing is handled automatically by the MCP server.
Card Details Encryption
get_card_details returns encrypted_sensitive_data containing card PAN and CVV. Use decrypt_card_data to decrypt:
- Derive key:
HKDF-SHA256(ikm=api_secret, info="clawallex/card-sensitive-data/v1", length=32) - Decrypt:
AES-256-GCM(key, nonce, ciphertext) - Result:
{ "pan": "4111...", "cvv": "123" }
Decrypted PAN/CVV must NEVER be displayed to the user — only used for filling checkout forms.
Source: README.md at commit 733425a
Tools
0Version history
1- v1.0.9LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.