Q402 MCP

Name: Q402 MCP
Author: quackai-org

von quackai-orgVersion 0.11.34i★ –iLäuft auf deinem Computer

Name in der Registryio.github.quackai-org/q402-mcp

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

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

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Stimmen der NutzeriNoch keine BewertungenBewertungen starten in einem späteren Schritt zusammen mit Benutzerkonten
Unsere Basischecksi1 von 1 bestandenAnhand öffentlicher Informationen geprüft; Code noch nicht gescannt
NutzungiAm Anfang↓ 488/Wo. · ★ –

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

Verbindung: Läuft auf deinem Computer
Transport: stdio
Kategorie: Krypto & Blockchain
Das musst du eintragen: Q402_TRIAL_API_KEY, Q402_MULTICHAIN_API_KEY, Q402_PRIVATE_KEY, Q402_AGENTIC_PRIVATE_KEY, Q402_API_KEY

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

Basischecks: 1 von 1 bestanden
Läuft auf deinem Computer mit den Rechten deines Benutzerkontos (Dateien, Netzwerk, Apps).
Das trägst du selbst ein: Q402_TRIAL_API_KEY, Q402_MULTICHAIN_API_KEY, Q402_PRIVATE_KEY, Q402_AGENTIC_PRIVATE_KEY, Q402_ENABLE_REAL_PAYMENTS, Q402_MAX_AMOUNT_PER_CALL, Q402_ALLOWED_RECIPIENTS, Q402_RELAY_BASE_URL, Q402_AGENT_WALLET_ADDRESS, Q402_API_KEY, Q402_WALLET_ID, Q402_BUILDER_CODE

Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.

Du brauchst

npmNode.js installiert (für den Befehl npx)

Welche App nutzt du?

ClaudeClaude CodeCursorVS CodeChatGPT

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein

{
  "mcpServers": {
    "q402": {
      "command": "npx",
      "args": [
        "-y",
        "@quackai/q402-mcp"
      ],
      "env": {
        "Q402_TRIAL_API_KEY": "your-value",
        "Q402_MULTICHAIN_API_KEY": "your-value",
        "Q402_PRIVATE_KEY": "your-value",
        "Q402_AGENTIC_PRIVATE_KEY": "your-value",
        "Q402_ENABLE_REAL_PAYMENTS": "your-value",
        "Q402_MAX_AMOUNT_PER_CALL": "your-value",
        "Q402_ALLOWED_RECIPIENTS": "your-value",
        "Q402_RELAY_BASE_URL": "your-value",
        "Q402_AGENT_WALLET_ADDRESS": "your-value",
        "Q402_API_KEY": "your-value",
        "Q402_WALLET_ID": "your-value",
        "Q402_BUILDER_CODE": "your-value"
      }
    }
  }
}

Führe das in deinem Terminal aus

claude mcp add q402 --env Q402_TRIAL_API_KEY=your-value --env Q402_MULTICHAIN_API_KEY=your-value --env Q402_PRIVATE_KEY=your-value --env Q402_AGENTIC_PRIVATE_KEY=your-value --env Q402_ENABLE_REAL_PAYMENTS=your-value --env Q402_MAX_AMOUNT_PER_CALL=your-value --env Q402_ALLOWED_RECIPIENTS=your-value --env Q402_RELAY_BASE_URL=your-value --env Q402_AGENT_WALLET_ADDRESS=your-value --env Q402_API_KEY=your-value --env Q402_WALLET_ID=your-value --env Q402_BUILDER_CODE=your-value -- npx -y @quackai/q402-mcp

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "q402": {
      "command": "npx",
      "args": [
        "-y",
        "@quackai/q402-mcp"
      ],
      "env": {
        "Q402_TRIAL_API_KEY": "your-value",
        "Q402_MULTICHAIN_API_KEY": "your-value",
        "Q402_PRIVATE_KEY": "your-value",
        "Q402_AGENTIC_PRIVATE_KEY": "your-value",
        "Q402_ENABLE_REAL_PAYMENTS": "your-value",
        "Q402_MAX_AMOUNT_PER_CALL": "your-value",
        "Q402_ALLOWED_RECIPIENTS": "your-value",
        "Q402_RELAY_BASE_URL": "your-value",
        "Q402_AGENT_WALLET_ADDRESS": "your-value",
        "Q402_API_KEY": "your-value",
        "Q402_WALLET_ID": "your-value",
        "Q402_BUILDER_CODE": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "q402": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@quackai/q402-mcp"
      ],
      "env": {
        "Q402_TRIAL_API_KEY": "your-value",
        "Q402_MULTICHAIN_API_KEY": "your-value",
        "Q402_PRIVATE_KEY": "your-value",
        "Q402_AGENTIC_PRIVATE_KEY": "your-value",
        "Q402_ENABLE_REAL_PAYMENTS": "your-value",
        "Q402_MAX_AMOUNT_PER_CALL": "your-value",
        "Q402_ALLOWED_RECIPIENTS": "your-value",
        "Q402_RELAY_BASE_URL": "your-value",
        "Q402_AGENT_WALLET_ADDRESS": "your-value",
        "Q402_API_KEY": "your-value",
        "Q402_WALLET_ID": "your-value",
        "Q402_BUILDER_CODE": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

Q402_TRIAL_API_KEY geheim env
Recommended 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 secret…
Q402_MULTICHAIN_API_KEY geheim env
Recommended 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 secret…
Q402_PRIVATE_KEY geheim env
Mode 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 s…
Q402_AGENTIC_PRIVATE_KEY geheim env
Mode 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 li…
Q402_ENABLE_REAL_PAYMENTS env
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 AP…
Q402_MAX_AMOUNT_PER_CALL env
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 + co…
Q402_ALLOWED_RECIPIENTS env
Optional comma-separated lowercase EVM addresses. When set, q402_pay rejects any recipient not on this allowlist.
Q402_RELAY_BASE_URL env
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 env
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 t…
Q402_API_KEY geheim env
DEPRECATED 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_TRI…
Q402_WALLET_ID env
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_WALLE…
Q402_BUILDER_CODE env
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…

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026

✓ Bestanden
Entwickler passt zum Repo
Der Registry-Name wurde mit dem GitHub-Konto quackai-org bestätigt, dem das Repo gehört
… Noch nicht geprüft
Wird noch gepflegt
Dieses Repo haben wir noch nicht von GitHub gelesen
… Noch nicht geprüft
Hat eine Lizenz
Dieses Repo haben wir noch nicht von GitHub gelesen
– Nicht zutreffend
Endpunkt antwortet
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
– Nicht zutreffend
Anmeldung mit OAuth
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
… Noch nicht geprüft
Keine versteckten Anweisungen in Tool-Beschreibungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen

Im Vergleich mit anderen in Krypto & Blockchaini

Mehr Sterne als 0 % der anderen 1614 Server in dieser Kategorie
Neuer in der Registry veröffentlicht als 92 % der anderen 1614 Server in dieser Kategorie
Basischecks gleich gut wie oder besser als bei 100 % der anderen 1614 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Q402 MCP sicher?

Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Das musst du eintragen: Q402_TRIAL_API_KEY, Q402_MULTICHAIN_API_KEY, Q402_PRIVATE_KEY, Q402_AGENTIC_PRIVATE_KEY, Q402_API_KEY

Läuft er auf meinem Computer oder in der Cloud?

Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.11.34) kam vor 5 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Highwire, Crypto Sentiment X402, Crypto MCP Server

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Highwire

Trade, launch and research higher.fun coins on Solana, from any AI agent. Unsigned or policy-signed.

von HigherMaestroWachsend↓ 1729/Wo.Aktualisiert heute

Computer oder Cloud✓ highwire.fun

Installieren

Crypto Sentiment X402

Crypto news sentiment for 24 coins: label, score and headlines behind it, paid per call via x402

von whatevercat-creatorGanz neu↓ 61/Wo.Aktualisiert heute

Läuft auf deinem Computer

Installieren

Crypto MCP Server

Live cryptocurrency prices and FX rates as agent tools.

von thenextgennexus.comGanz neuAktualisiert heute

Läuft in der Cloud✓ thenextgennexus.com

Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

@quackai/q402-mcp

MCP server for Q402 - gasless USDC, USDT, RLUSD, and USDG payments across 12 EVM chains (USDG on Robinhood Chain), callable from Claude (Desktop / Code), OpenAI Codex CLI, and any other Model Context Protocol client.

Free trial available. 500 gasless transactions on BNB Chain + Base (USDC + USDT), no card. One wallet signature: https://q402.quackai.ai.

Limited-time bonus: Mantle (USDC + USDT) is also covered by trial keys during 2026-08-21~08-28 UTC+9.

Trial-scope policy: API keys minted under the free-trial program (plan: "trial") settle on BNB Chain (USDC/USDT gasless) and Base (USDC/USDT gasless) as permanent chains. Avalanche trial has ended — use a Multichain key for avax. Mantle (USDC/USDT gasless) is covered during the limited-time window 2026-08-21~08-28 UTC+9 — server-side time enforcement, returns TRIAL_BNB_ONLY outside the window. Paid API keys see the full 12-chain matrix at all times.

Quote → route → (optional) settle stablecoin payments across 12 EVM chains, from any MCP client. Recipient gets the full amount; sender pays $0 gas via Q402's EIP-7702 relayer.

Quick start

Register the server with your client (one-line per client).
Say "Set up Q402" to your agent. It runs q402_doctor → creates ~/.q402/mcp.env → walks you through pasting keys.

1. Register the server

Client	Command / config
Claude Code (CLI)	`claude mcp add q402 -- npx -y @quackai/q402-mcp`
Claude Desktop (app)	Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): `{ "mcpServers": { "q402": { "command": "npx", "args": ["-y", "@quackai/q402-mcp"] } } }`. Restart the app.
OpenAI Codex CLI	`codex mcp add q402 -- npx -y @quackai/q402-mcp` (Windows fallback: see below)
Cursor	Add to `~/.cursor/mcp.json`: `{ "mcpServers": { "q402": { "command": "npx", "args": ["-y", "@quackai/q402-mcp"] } } }`
Cline	Cline → Settings → MCP Servers → Edit JSON. Same shape as Cursor.
GitHub Copilot (VS Code)	Add to `.vscode/mcp.json` - root key is `servers`, not `mcpServers`: `{ "servers": { "q402": { "command": "npx", "args": ["-y", "@quackai/q402-mcp"] } } }`. Reload VS Code, then enable q402 in the Copilot Chat tools picker.
Hermes Agent (Nous Research)	YAML, not JSON. Add under `mcp_servers` in `~/.hermes/config.yaml` (see below), then run `/reload-mcp`.
Any other stdio MCP client	Point it at `npx -y @quackai/q402-mcp`. No client-specific code.

Hermes Agent - YAML config ( ~/.hermes/config.yaml )

Hermes reads MCP servers from ~/.hermes/config.yaml under mcp_servers (YAML, not JSON):

mcp_servers:

q402: command: "npx" args: ["-y", "@quackai/q402-mcp"] enabled: true

After editing, run /reload-mcp in Hermes to load the tools. Or use the CLI: hermes mcp add q402 --command npx --args -y @quackai/q402-mcp.

Claude Code (the CLI, claude binary) and Claude Desktop (the macOS / Windows app) are different products. The claude mcp add command only exists in the CLI; the Desktop app needs the JSON config above.

Secrets are NOT in this config. The server reads them from ~/.q402/mcp.env (same pattern as AWS / Stripe / gh CLIs).

Windows: codex mcp add returns "Access is denied"

Some Windows setups block codex.exe from writing its own config. Add the stanza to ~/.codex/config.toml by hand:

[mcp_servers.q402]

command = "npx" args = ["-y", "@quackai/q402-mcp"]

Then restart Codex. Same effect as codex mcp add q402 -- npx -y @quackai/q402-mcp.

2. First-time setup

Restart your client, ask: > *"Set up Q402"*

The agent runs q402_doctor. On first install:

Creates ~/.q402/mcp.env (placeholders)
Opens it in your editor
Walks you through pasting an API key + a signing path into the file, not into chat
Restart + re-run q402_doctor to verify

Keys never paste into chat. Local modes sign on your machine; the key never leaves the device. Mode C (server-managed) needs no PK on the client.

Pick a signing mode

Mode	Env	Signer	Notes
A	`Q402_PRIVATE_KEY`	MetaMask EOA, local	Simplest. Shows "Smart account" after first use (reversible via `q402_clear_delegation`). After EIP-7702 delegation to an older implementation, `q402_x402_fetch` is unavailable until `q402_clear_delegation` is called (gasless, reversible; next `q402_pay` re-delegates). If delegated to the current ERC-1271-capable implementation, `q402_x402_fetch` works normally.
B	`Q402_AGENTIC_PRIVATE_KEY`	Agent Wallet, local	Export PK from the dashboard → Wallets → Danger Zone → Export private key. MetaMask untouched.
C	(just an API key)	Agent Wallet, server-managed	No PK on the client. One-shot pays accept Trial or Multichain keys; recurring needs Multichain on every chain (BNB included).

When more than one mode is set, q402_pay asks the user which to use. Picker: walletMode = "agentic-server" \| "agentic-local" \| "eoa".

Manual setup (no AI)

Create ~/.q402/mcp.env yourself with the template below. Live mode only flips when an API key + a signing path are populated, so saving the template as-is stays in sandbox. Q402_ENABLE_REAL_PAYMENTS=0 forces sandbox even with real keys.

# ~/.q402/mcp.env

── API key (pick one or both for auto-routing) ──

Q402_TRIAL_API_KEY= # Free Trial, BNB (permanent) + Base (permanent) + Mantle limited-time (from /event) Q402_MULTICHAIN_API_KEY= # Paid Multichain, all 12 chains (from /payment)

── Signing path - pick ONE of Mode A / B / C ──

Mode A: your MetaMask EOA's hex private key.

Hardware wallets (Ledger / Trezor) are NOT supported here - Q402

needs a raw hex key it can sign EIP-7702 type-4 authorizations with.

Q402_PRIVATE_KEY=

Mode B: exported Agent Wallet pk from the dashboard. Keeps your

MetaMask untouched. Get it at:

https://q402.quackai.ai/dashboard → Agent tab → Export

Q402_AGENTIC_PRIVATE_KEY=

Mode C: no PK needed. A Trial key also enables Mode C one-shot payments;

leave both PK lines blank. Q402 signs with the server-managed Agent Wallet.

Multichain key required for recurring, Mode C batch, and bridge/OFT.

Optional: pin one of your Agent Wallets when you have multiple (max 10).

Q402_AGENT_WALLET_ADDRESS=0x...

Live mode switch:

0 = sandbox (test mode, no funds move)

1 = real on-chain payments

Default 1 - safe because mode only flips to live when an API key AND

at least one valid signing path (A/B/C) are populated above.

Q402_ENABLE_REAL_PAYMENTS=1

Default Q402 deployment. Only change for self-hosted.

Q402_RELAY_BASE_URL=https://q402.quackai.ai/api

Safety guards (max-amount ships uncommented at $200; lower for tighter caps):

Q402_MAX_AMOUNT_PER_CALL=200

Q402_ALLOWED_RECIPIENTS=0xabc...,0xdef...

Pre-check (automatic trust-check before outgoing payments in live mode).

Triggers when paying a first-time counterparty OR amount >= $1.

Fee: $0.02 per check; verdict cached 7 days (no repeat charge within TTL).

Set to 1 to disable pre-check entirely (even first-time / large-amount pays).

Q402_DISABLE_PRECHECK=0

Then chmod 600 ~/.q402/mcp.env (Unix) and restart your client. That's the full configuration. Heads up on the EIP-7702 side effect: after your first live payment on a chain, your wallet will show 'Smart account' in MetaMask / OKX - that's the delegation Q402 uses for gasless settlement, reversible anytime via q402_clear_delegation. Important for x402 users: if EIP-7702 delegation is active on an older implementation, q402_x402_fetch cannot sign x402 payments until you call q402_clear_delegation (gasless on Base, reversible — the next q402_pay re-delegates automatically). Wallets delegated to the current ERC-1271-capable implementation work normally.

Advanced - explicit env injection

If you'd rather skip the file and inject env vars yourself (e.g. via Codex env_vars allow-list, a secrets manager, or shell exports), the server falls through to process.env - and process.env wins over file values on conflicts. So existing shell-export setups keep working unchanged.

Codex env_vars allow-list example

[mcp_servers.q402]

command = "npx" args = ["-y", "@quackai/q402-mcp"] startup_timeout_sec = 20.0 env_vars = [ "Q402_TRIAL_API_KEY", "Q402_MULTICHAIN_API_KEY", "Q402_PRIVATE_KEY", "Q402_AGENTIC_PRIVATE_KEY", "Q402_AGENT_WALLET_ADDRESS", "Q402_ENABLE_REAL_PAYMENTS", "Q402_RELAY_BASE_URL", ]

Then export the values in ~/.zshrc / ~/.bashrc. See the Codex config reference for the full schema.

Try it without any setup

q402_quote works with zero configuration - no API key, no private key, no env file. Ask:

*"Compare gas costs to send 50 USDC to vitalik.eth across all 12 Q402 chains."*

Q402_RELAY_BASE_URL overrides the relay endpoint. Set it explicitly when running against a self-hosted Q402 deployment or a non-canonical environment.

Tools exposed

52 tools, grouped by capability. Read-only by default; live mode needs a live API key, a signing path, and Q402_ENABLE_REAL_PAYMENTS=1. Rows marked live mode move funds and need an explicit in-chat confirmation.

Tool	Auth	Purpose
Payments & wallet
`q402_doctor`	none	First-install onboarding + ongoing health check (per-scope quota, EIP-7702 state, relay reachability, slot-mismatch warnings).
`q402_quote`	none	Compare gas + supported tokens across chains.
`q402_balance`	api key	Verify key + remaining quota.
`q402_pay`	live mode	Single-recipient gasless transfer. Sandbox by default. In live mode, automatically runs a trust-check ($0.02) on the recipient before each payment when it is a first-time counterparty or the amount ≥ $1; verdict cached 7 days (no double-charge within TTL). Degrades to free basic verdict only when wallet balance exactly covers the transfer but not the $0.02 fee, or when only a non-USDC rail token is available. Pre-check never blocks the main transaction. Disable with `Q402_DISABLE_PRECHECK=1`.
`q402_batch_pay`	live mode	Up to 20 recipients per call. Trial: 5 - applies when paying with your own key (Mode A/B); server-managed Agent Wallet (Mode C) batch is paid Multichain-only. Same auto-routing as `q402_pay`. 6+ BNB batches with Trial set return `status="ambiguous"` so the agent asks how to split. xlayer + stable not batchable - use `q402_pay` in a loop.
`q402_receipt`	none	Fetch + locally verify a Trust Receipt (`rct_…` id, ECDSA against the relayer EOA).
`q402_wallet_status`	private key	Per-chain EIP-7702 state for the EOA derived from `Q402_PRIVATE_KEY`.
`q402_clear_delegation`	private key / api key	Clear EIP-7702 delegation (Mode A/B local key OR Mode C api key, server-signed). Sponsored on every chain except Ethereum (billed to your Gas Tank). Two-phase consent (`consentToken`).
`q402_agentic_info`	api key	Agent Wallet info (addresses, per-wallet caps, daily-spend used, ERC-8004 id). Drives Mode C.
Treasury memory
`q402_memory_summary`	api key	Treasury overview over a window: USD-stablecoin spend by chain/source, top vendors, schedules, open requests/escrow, failures. Read-only.
`q402_vendor_history`	api key	Total paid to one vendor (or a vendor leaderboard) with recurring cadence. Read-only.

| q402_agent_spend_report | api ke

Nur der Anfang wird gezeigt; den Rest findest du im Repo

Q402 MCP

Überblick

Die drei Säulen von PopNx MCP

Was du damit machen kannst

Installation

Bevor du installierst

Werte, die du selbst einträgst

Was er kann

Basischecksi

Entwickler passt zum Repo

Wird noch gepflegt

Hat eine Lizenz

Endpunkt antwortet

Anmeldung mit OAuth

Keine versteckten Anweisungen in Tool-Beschreibungen

Im Vergleich mit anderen in Krypto & Blockchaini

Häufige Fragen

Alternativen

Highwire

Crypto Sentiment X402

Crypto MCP Server

README vom Entwickler

@quackai/q402-mcp

Quick start

1. Register the server

2. First-time setup

Pick a signing mode

Manual setup (no AI)

── API key (pick one or both for auto-routing) ──

── Signing path - pick ONE of Mode A / B / C ──

Mode A: your MetaMask EOA's hex private key.

Hardware wallets (Ledger / Trezor) are NOT supported here - Q402

needs a raw hex key it can sign EIP-7702 type-4 authorizations with.

Mode B: exported Agent Wallet pk from the dashboard. Keeps your

MetaMask untouched. Get it at:

https://q402.quackai.ai/dashboard → Agent tab → Export

Mode C: no PK needed. A Trial key also enables Mode C one-shot payments;

leave both PK lines blank. Q402 signs with the server-managed Agent Wallet.

Multichain key required for recurring, Mode C batch, and bridge/OFT.

Optional: pin one of your Agent Wallets when you have multiple (max 10).

Q402_AGENT_WALLET_ADDRESS=0x...

Live mode switch:

0 = sandbox (test mode, no funds move)

1 = real on-chain payments

Default 1 - safe because mode only flips to live when an API key AND

at least one valid signing path (A/B/C) are populated above.

Default Q402 deployment. Only change for self-hosted.

Safety guards (max-amount ships uncommented at $200; lower for tighter caps):

Q402_ALLOWED_RECIPIENTS=0xabc...,0xdef...

Pre-check (automatic trust-check before outgoing payments in live mode).

Triggers when paying a first-time counterparty OR amount >= $1.

Fee: $0.02 per check; verdict cached 7 days (no repeat charge within TTL).

Set to 1 to disable pre-check entirely (even first-time / large-amount pays).

Q402_DISABLE_PRECHECK=0

Advanced - explicit env injection

Try it without any setup

Tools exposed