Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • A tool description tries to instruct the AI assistant
Own this project? Claim it
Q402 MCP logo

Q402 MCP

Gasless stablecoin payments, recurring transfers, bridges, yield positions, and treasury reporting across 12 EVM chains.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Q402 MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "q402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@quackai/q402-mcp"
      ],
      "env": {
        "Q402_TRIAL_API_KEY": "YOUR_VALUE_HERE",
        "Q402_MULTICHAIN_API_KEY": "YOUR_VALUE_HERE",
        "Q402_PRIVATE_KEY": "YOUR_VALUE_HERE",
        "Q402_AGENTIC_PRIVATE_KEY": "YOUR_VALUE_HERE",
        "Q402_AGENT_WALLET_ADDRESS": "YOUR_VALUE_HERE",
        "Q402_ENABLE_REAL_PAYMENTS": "YOUR_VALUE_HERE",
        "Q402_RELAY_BASE_URL": "YOUR_VALUE_HERE",
        "Q402_MAX_AMOUNT_PER_CALL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 48 tools correctly (6d ago).

Overview

The q402-mcp MCP server connects MCP clients to Q402 for gasless stablecoin payments across 12 EVM chains. It provides tools for quoting, sending, batching, verifying, and scheduling transfers, plus bridge quotes, yield data, wallet state, and treasury reports. Local signing uses an EOA or exported Agent Wallet key, while server-managed Agent Wallet mode can operate without a client-side private key. Reach for it when an agent needs controlled stablecoin payments or payment operations through a standard stdio MCP connection.

Use cases

  • Send gasless stablecoin payments from an MCP client
  • Schedule recurring payments to vendors
  • Compare chains and tokens before settling a transfer
  • Bridge USDC or USDT0 between supported chains
  • Review Agent Wallet spending and yield positions

Key features

  • Gasless payments across 12 EVM chains
  • Single and batch stablecoin transfers
  • Recurring payment rule management
  • CCIP and LayerZero bridge operations
  • Treasury, vendor, and wallet spend reporting
  • Curated lending market and yield position data

Tools48

What Q402 MCP lets your agent do. Expand a tool for its parameters.

Verified live~20.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

What it can do

From the 48 tools this server returned when we ran it.

Runs commands · 5Can delete or modify data · 1Writes files · 1Handles credentials · 33Makes network requests · 11Read-only tools · 42
Unusual tool instructions. 2 tool descriptions contain text aimed at the AI model rather than at you (tries to chain into other tools; asks the assistant to hide something from the user). Read the tool descriptions before connecting.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age167 days
Maintainers2

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @quackai/q402-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.2kPackage downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed48Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Q402 MCP works

What q402-mcp MCP server does

The q402-mcp MCP server exposes Q402 payment and treasury operations as MCP tools. It supports gasless transfers of supported stablecoins across 12 EVM chains, with the recipient receiving the full amount while Q402 handles relaying. The available payment flow includes chain and token quotes, balance checks, single-recipient payments, batches of up to 20 recipients, and locally verifiable Trust Receipts.

Beyond one-time payments, the server can manage recurring payment rules, including creation, listing, pausing, resuming, skipping the next execution, cancellation, and inspection of recent fires. Read-only reporting tools summarize stablecoin spend, vendors, Agent Wallet usage, schedules, escrow requests, and failures.

How it works

The server runs as a stdio MCP process, normally started with npx -y @quackai/q402-mcp. An MCP client invokes tools, while Q402 provides routing and relaying through its configured deployment. Payments are sandboxed by default. Real on-chain activity requires an API key, a valid signing path, and Q402_ENABLE_REAL_PAYMENTS=1.

Three signing modes are supported. Mode A signs with a local EOA private key, Mode B signs with a locally stored Agent Wallet key, and Mode C uses a server-managed Agent Wallet without a private key on the client. Local payment modes use EIP-7702 delegation; wallet status and delegation cleanup are available through dedicated tools. Live payments may also run an automatic recipient trust check for first-time counterparties or transfers of at least $1, with results cached for seven days.

Setup and configuration

Register the server in the MCP client’s configuration, then ask the agent to set up Q402. The onboarding check creates ~/.q402/mcp.env, guides key entry into that file rather than chat, and verifies the configuration after restart. Manual setup is also supported. File values can be overridden by environment variables supplied directly by the process environment.

Use a trial API key for the trial scope or a Multichain API key for the full 12-chain matrix. Trial coverage permanently includes BNB Chain and Base for USDC and USDT; the documented Mantle trial coverage is time-limited. Multichain access is required for recurring payments, Mode C batches, and bridge or OFT operations.

Relevant settings include Q402_PRIVATE_KEY, Q402_AGENTIC_PRIVATE_KEY, Q402_AGENT_WALLET_ADDRESS, Q402_TRIAL_API_KEY, Q402_MULTICHAIN_API_KEY, Q402_ENABLE_REAL_PAYMENTS, Q402_RELAY_BASE_URL, and Q402_MAX_AMOUNT_PER_CALL. Hardware wallets are not supported for the local private-key signing paths because Q402 requires a raw hexadecimal key.

Tools and capabilities

The q402-mcp MCP server includes tools for:

  • Comparing gas and token availability, checking balances and quotas, and running installation or health diagnostics.
  • Sending individual or batched payments and retrieving or verifying Trust Receipts.
  • Inspecting EIP-7702 wallet state and clearing delegation with two-phase consent.
  • Managing recurring payment rules and reviewing their recent executions.
  • Quoting and sending CCIP USDC bridges or LayerZero USDT0 transfers from a server-managed Agent Wallet.
  • Listing curated lending markets and viewing Agent Wallet yield positions.
  • Reading treasury summaries, vendor history, and per-wallet spend reports.

Bridge history and Bridge Gas Tank tools currently return dashboard guidance for operations that require owner-signature authentication. The bridge send tools remain sandbox-first; live execution requires the documented confirmation, key, and live-payment settings.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Q402 MCP

q402-mcp is an MCP server that connects AI clients to Q402’s gasless payment relayer across 12 EVM chains. Its main tools quote, send, batch, verify, and schedule stablecoin payments, while also covering wallet status, bridges, treasury reports, and yield positions. It runs through a standard stdio MCP configuration.

Install it by registering `npx -y @quackai/q402-mcp` as a stdio MCP server in your client. Restart the client and ask the agent to set up Q402; `q402_doctor` creates `~/.q402/mcp.env` and guides key configuration.

Yes, q402-mcp works with Cursor through `~/.cursor/mcp.json`. Add a server named `q402` with command `npx` and arguments `-y @quackai/q402-mcp`, then reload or restart Cursor.

Leave the configuration in sandbox mode by setting `Q402_ENABLE_REAL_PAYMENTS=0`, or avoid populating a complete live API-key and signing-path combination. Payments are sandboxed by default, and the live switch is required for real on-chain activity.

Yes, Mode C uses a server-managed Agent Wallet and does not require a private key on the client. One-shot payments can use a trial or Multichain key, while recurring payments, Mode C batches, and bridge or OFT operations require a Multichain key.

Related MCP servers

All in Code Execution All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewQ402 MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/q402-mcp?style=directory)](https://allmcps.com/mcp/q402-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/q402-mcp"><img src="https://allmcps.com/api/badge/q402-mcp?style=directory" alt="Q402 MCP on AllMCPs" /></a>