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

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated 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.
Before you install
The server can spend real money from your USDC wallet and create or refill cards, so amounts and limits deserve review. It handles full card numbers and CVVs, which the README says must never be shown to the user. The API secret signs requests and also derives the card-data decryption key. The client ID is bound on first use and cannot be changed; losing it means losing access to cards created under it.

Installation

In SourceWeft

  1. Open Clawallex Mcp in the dashboard and add it to a workspace.
  2. 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

bash
npm install -g @clawallex/mcp-server

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:

json
{  "mcpServers": {    "clawallex": {      "command": "npx",      "args": ["@clawallex/mcp-server"],      "env": {        "CLAWALLEX_API_KEY": "your_api_key",        "CLAWALLEX_API_SECRET": "your_api_secret"      }    }  }}
Claude Code
bash
claude mcp add --scope local clawallex -- npx @clawallex/mcp-server \  --api-key your_api_key \  --api-secret your_api_secret
Codex CLI

Add to your ~/.codex/config.toml or .codex/config.toml:

toml
[mcp_servers.clawallex]command = "npx"args = [  "@clawallex/mcp-server",  "--api-key",  "your_api_key",  "--api-secret",  "your_api_secret",]
Gemini CLI

Add to your ~/.gemini/settings.json:

json
{  "mcpServers": {    "clawallex": {      "command": "npx",      "args": [        "@clawallex/mcp-server",        "--api-key", "your_api_key",        "--api-secret", "your_api_secret"      ]    }  }}
OpenCode

Add to your opencode.json:

json
{  "mcp": {    "clawallex": {      "type": "local",      "command": ["npx", "@clawallex/mcp-server", "--api-key", "your_api_key", "--api-secret", "your_api_secret"],      "enabled": true    }  }}

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:

clawallex_setup     → should show "ready" with bound client_idget_wallet          → should return wallet balancelist_cards          → should return card list (empty if no cards yet)

Typical Flows

Payment Flow (Mode A — Wallet Balance)

1. clawallex_setup                           → verify connection & bind identity2. get_wallet                                → check USDC balance3. clawallex_pay({ amount, description })    → create a one-time virtual card4. get_card_details({ card_id })             → get encrypted card data5. decrypt_card_data({ nonce, ciphertext })  → decrypt PAN/CVV for checkout

Subscription Flow

1. clawallex_setup                                          → verify connection2. get_wallet                                               → check USDC balance3. clawallex_subscribe({ initial_amount, description })     → create reloadable card4. get_card_details({ card_id })                            → get card number5. clawallex_refill({ card_id, amount })                    → top up when needed

Tools

High-Level (Recommended)

ToolDescription
clawallex_setupCheck connection status and bind agent identity
clawallex_payOne-time payment — creates a single-use virtual card
clawallex_subscribeRecurring subscription — creates a reloadable card
clawallex_refillTop up a subscription card balance

Identity & Binding

ToolDescription
whoamiQuery current API Key binding status (read-only)
bootstrapBind a client_id to this API Key

Wallet & Query

ToolDescription
get_walletGet wallet balance and status
get_wallet_recharge_addressesGet on-chain USDC deposit addresses
list_cardsList virtual cards created by this agent
get_card_balanceGet card balance and status
batch_card_balancesCheck balances for multiple cards in one call
update_cardUpdate card risk controls (tx_limit, allowed_mcc, blocked_mcc)
get_card_detailsGet card details including risk controls, cardholder info, and encrypted PAN/CVV
decrypt_card_dataDecrypt PAN/CVV from get_card_details
list_transactionsList card transactions with optional filters

Advanced (x402 On-Chain)

ToolDescription
get_x402_payee_addressGet on-chain receiving address for x402 payments
create_card_orderCreate a card with full control (supports Mode B two-stage)
refill_cardRefill a stream card with x402 or custom idempotency keys

CLI Options

OptionEnv VariableRequiredDefaultDescription
--api-keyCLAWALLEX_API_KEYYes—Clawallex API Key
--api-secretCLAWALLEX_API_SECRETYes—Clawallex API Secret (HMAC-SHA256 signing)
--base-urlCLAWALLEX_BASE_URLNohttps://api.clawallex.comAPI base URL
--client-idCLAWALLEX_CLIENT_IDNoauto-generatedAgent identity UUID. See Client ID section.
--transport—NostdioTransport mode: stdio, sse, http
--port—No18080HTTP port for sse / http transport

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_setup automatically calls bootstrap to bind client_id on first use
  • Once bound, the client_id cannot 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:

  1. --client-id <value> CLI argument (must be >= 36 characters)
  2. ~/.clawallex-mcp/client_ids.json local file (from a previous run)
  3. 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)

bash
npx @clawallex/mcp-server \  --api-key your_api_key \  --api-secret your_api_secret

SSE (remote agent, compatible with older MCP clients)

bash
npx @clawallex/mcp-server \  --api-key your_api_key \  --api-secret your_api_secret \  --transport sse \  --port 18080

Agent connects to: http://localhost:18080/sse

Streamable HTTP (MCP SDK 1.0+ recommended)

bash
npx @clawallex/mcp-server \  --api-key your_api_key \  --api-secret your_api_secret \  --transport http \  --port 18080

Agent connects to: http://localhost:18080/mcp

Local Development

bash
npm installnpm run build
# List all tools (stdio)echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \  | node dist/index.js \    --api-key your_api_key \    --api-secret your_api_secret \  2>/dev/null

Security

Authentication

Every API request is signed with HMAC-SHA256:

canonical = METHOD + "\n" + PATH + "\n" + TIMESTAMP + "\n" + hex(sha256(body))X-Signature = base64(hmac_sha256(api_secret, canonical))

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:

  1. Derive key: HKDF-SHA256(ikm=api_secret, info="clawallex/card-sensitive-data/v1", length=32)
  2. Decrypt: AES-256-GCM(key, nonce, ciphertext)
  3. 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

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