Skip to content
mcp/skillhub

Q402 MCP Server

by quackai-orgio.github.quackai-org/q402-mcpv0.11.23

Q402 - gasless payments, yield, escrow, bridge & NAV triggers on 12 EVM chains. Sandbox-default.

0Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active19d ago

Install Q402 MCP server

Install in Claude Code

claude mcp add q402 -e Q402_TRIAL_API_KEY='<q402-trial-api-key>' -e Q402_MULTICHAIN_API_KEY='<q402-multichain-api-key>' -e Q402_PRIVATE_KEY='<q402-private-key>' -e Q402_AGENTIC_PRIVATE_KEY='<q402-agentic-private-key>' -e Q402_API_KEY='<q402-api-key>' -- npx -y @quackai/q402-mcp

Configuration

VariableRequiredSecretDescription
Q402_TRIAL_API_KEY—yesRecommended path: skip this UI and run `q402_doctor` after install - it stores secrets in ~/.q402/mcp.env, which the server auto-loads. Fill this field directly ONLY if your MCP client manages secrets for you. Value is a Free Trial API key from https://q402.quackai.ai/event - BNB Chain (permanent) + Base (permanent) + Mantle limited-time (2026-08-21~08-28 UTC+9), 500 sponsored TXs, gas covered by Q402. Avalanche trial has ended. BNB and Base payments auto-route to this key when set (same rule for q402_pay and q402_batch_pay up to 5 recipients).
Q402_MULTICHAIN_API_KEY—yesRecommended path: skip this UI and run `q402_doctor` after install - it stores secrets in ~/.q402/mcp.env, which the server auto-loads. Fill this field directly ONLY if your MCP client manages secrets for you. Value is a Paid Multichain API key from https://q402.quackai.ai/payment - full 12-chain support with per-chain Gas Tank. Auto-routed for non-BNB payments and whenever keyScope='multichain' is chosen.
Q402_PRIVATE_KEY—yesMode A - real EOA signing. Hex-encoded EVM private key (0x + 64 hex chars) of YOUR MetaMask wallet, used to sign payment authorizations LOCALLY on your machine. After your first payment that wallet shows as 'Smart account' in MetaMask (EIP-7702 delegation, reversible via q402_clear_delegation). Use a fresh wallet, not your main one. Skip this and pick Mode B (Q402_AGENTIC_PRIVATE_KEY) or Mode C (server-managed Agent Wallet) if you'd rather keep your MetaMask untouched. Recommended path: run q402_doctor after install - it stores secrets in ~/.q402/mcp.env, which the server auto-loads.
Q402_AGENTIC_PRIVATE_KEY—yesMode B - local Agent Wallet signing. Hex-encoded EVM private key (0x + 64 hex chars) exported from your Agent Wallet at https://q402.quackai.ai/dashboard -> Agent tab -> Export. Signs LOCALLY just like Mode A, but the signer is your dedicated Agent Wallet - your MetaMask EOA is never touched. Pick this for AI-agent automation when you want a dedicated purse with per-tx + daily caps you set on the dashboard.
Q402_ENABLE_REAL_PAYMENTS——Live-mode switch. 0 = sandbox (test mode, no funds move - every q402_pay returns a fake hash). 1 = real on-chain payments. Default 1 since v0.5.11: safe because mode only flips to live when a live API key (q402_live_*) is set AND one of (a) a valid 32-byte private key for local signing modes, OR (b) walletMode="agentic-server" with Q402_MULTICHAIN_API_KEY for the server-managed Agent Wallet path. Without either combination, the server stays in sandbox regardless of this flag.
Q402_MAX_AMOUNT_PER_CALL——Per-call USD-equivalent cap for USDC/USDT/RLUSD. Any such q402_pay request with amount above this is rejected before signing. Q (QuackAI) is exempt by design (your own token; recipient allowlist + confirmation still apply). Lower this for a tighter agent blast-radius; raise for treasury-grade transfers.
Q402_ALLOWED_RECIPIENTS——Optional comma-separated lowercase EVM addresses. When set, q402_pay rejects any recipient not on this allowlist.
Q402_RELAY_BASE_URL——Override for the Q402 relay endpoint. Defaults to https://q402.quackai.ai/api. Set explicitly when running against a self-hosted Q402 deployment or a non-canonical environment.
Q402_AGENT_WALLET_ADDRESS——Server-managed Agent Wallet picker (walletMode='agentic-server' only). Lowercased agent wallet address (the hex 0x... shown on the Agent tab of your dashboard) selecting which of your Agent Wallets to spend from when you hold more than one (max 10 per owner). Omit to use the default wallet. Ignored for the local-signing modes that carry their own private key.
Q402_API_KEY—yesDEPRECATED legacy single-key env from pre-v0.5.0 installs. The server still reads it as a silent fallback so existing setups keep working, but new users should pick a scoped variant instead. Q402_TRIAL_API_KEY (Free Trial, BNB Chain + Base) and Q402_MULTICHAIN_API_KEY (full 12-chain surface) are designed to coexist - BNB and Base payments auto-route to the trial key, other chains use multichain. Only set Q402_API_KEY if you are migrating an existing pre-v0.5.0 install; do NOT set it alongside the scoped variants on a fresh install.
Q402_WALLET_ID——DEPRECATED soft-migration alias for Q402_AGENT_WALLET_ADDRESS (one release of overlap from v0.6.0). The server still accepts it but logs a deprecation notice. New installs should set Q402_AGENT_WALLET_ADDRESS directly.
Q402_BUILDER_CODE——Optional Base Builder Code for onchain attribution (ERC-8021 / Base Builder Codes). When set, every q402_x402_fetch payment includes your code as the client/intermediary in the x402 payment extension so payments are attributed onchain. Format: 1-32 lowercase letters, numbers, or underscores. Leave unset to disable attribution.

Freshness

Active — last maintenance signal 19d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-09-21 · 19d ago · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-08-19 · 52d ago · official registry · v0.11.23

FAQ

›How do I install the Q402 MCP server in Claude Code?

Run: claude mcp add q402 -e Q402_TRIAL_API_KEY='<q402-trial-api-key>' -e Q402_MULTICHAIN_API_KEY='<q402-multichain-api-key>' -e Q402_PRIVATE_KEY='<q402-private-key>' -e Q402_AGENTIC_PRIVATE_KEY='<q402-agentic-private-key>' -e Q402_API_KEY='<q402-api-key>' -- npx -y @quackai/q402-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Q402 require an API key?

Yes. It expects Q402_TRIAL_API_KEY, Q402_MULTICHAIN_API_KEY, Q402_PRIVATE_KEY, Q402_AGENTIC_PRIVATE_KEY, Q402_API_KEY, of which 5 are secrets.

›Can I use Q402 as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Q402 in the official MCP registry?

Yes, as io.github.quackai-org/q402-mcp.

Alternatives to Q402

Other finance & fintech MCP servers.

View all