io.github.quackai-org/q402-mcp
NPM · @QUACKAI/Q402-MCP
Q402 - gasless payments, yield, escrow, bridge & NAV triggers on 12 EVM chains. Sandbox-default.
Available components
Last scanned (23 hours ago)
Scores higher than 72% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 118 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to quackai-org/q402-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 17992 tokens (~346/item across 52 items; 52 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
Tool Safety25
- Injection-marker check failed: the description of tool "q402_x402_fetch" contains an instruction to conceal the call from the user, the text "Do NOT tell the user", at byte 2431 of that field. See how to fix → Fail
- 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "q402_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Package version: 0.11.33 → 0.11.34 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −9
- Malware scan: pass → unverified ▼ security
- Injection markers: pass → fail ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: quackai-org/q402-mcp security
- Schema quality: 316 → 351 ▼ functional
- Package version: 0.11.23 → 0.11.33 functional
- Package version: 0.11.15 → 0.11.23 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@quackai/q402-mcp@0.11.34
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | quackai-org/q402-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/quackai-org/q402-mcp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3662851896 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a7fa0bfbd416e0f70c118db232657ff70b7a9770c7dfc9eae010920200c5a1183efcc12d9b2b76968ff94f068bdcfdca3b3559b1a6812b9b703407de3 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 118 packages
| Packages resolved | 118 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
q402_yield_reserves ~220
READ-ONLY - list the Q402 Yield lending markets the Agent Wallet can supply into. Returns each market's protocol, chain, asset, asset address, position token, market address, and current supply APY (shown as a %). No auth required and no funds move - this is purely a preview of available yield. Reads the curated lending markets on BNB Chain, plus Base when a curated vault is configured; each market reports its own protocol/venue. Deposit/withdraw (q402_yield_deposit / q402_yield_withdraw) cover both: 'bnb' (USDC/USDT) and 'base' (USDC only). Pass an optional `chain` to filter; omit it to see every supported chain. Use this whenever the user asks 'where can I earn yield?' or 'what's the lending APY on <asset>?' before supplying.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional chain filter. Curated lending markets on 'bnb' and 'base'. Omit for all supported chains. |
No output schema declared.
No examples provided.
q402_yield_withdraw ~901
WRITE - MOVES FUNDS. Withdraws the Agent Wallet's supplied stablecoin (USDC / USDT) out of its Q402 Yield lending position back to the Agent Wallet. Pass amount="max" to withdraw the maximum currently redeemable (can be < full position under vault caps). Server-managed Agent Wallet path (Mode C): authenticated by the configured live Multichain API key - the server holds the encrypted key, signs the withdraw, and sponsors gas. CHAINS: 'bnb' (USDC or USDT); 'base' (USDC only). The venue is the chain's curated lending market and is reported in the receipt. Other chains are not yet available. ZIRCUIT IS QUEUED - withdrawing a Zircuit position (base USDC) files a withdrawal REQUEST: the result has status pending + a requestId, and USDC arrives in the Agent Wallet when Zircuit processes it (usually within 24 hours, up to 14 days). q402_yield_positions lists pending requests; q402_yield_cancel cancels one while it is pending. REQUIRES CONFIRMATION - like q402_pay, this tool refuses to execute unless `confirm: true` is set. Call it FIRST without confirm to get a one-line preview of exactly what will happen (amount, token, chain, wallet); show that to the user, get explicit approval, THEN re-call with confirm:true. Never set confirm:true on the user's behalf without that approval. SANDBOX BY DEFAULT - like q402_pay, no funds move unless a live Multichain key (q402_live_*) is configured AND Q402_ENABLE_REAL_PAYMENTS=1. Without both, confirm:true returns a sandbox preview (no on-chain withdraw) with a setup hint - confirm:true alone does NOT move real funds. RETRY SAFETY - on a timeout or an unconfirmed broadcast the tool returns status="uncertain" and echoes back the idempotencyKey it used. The withdrawal MAY have settled, so do NOT blindly call again - that starts a NEW withdrawal and can double-withdraw. To resume the SAME operation, re-call with idempotencyKey set to the echoed value; the server dedupes on it and replays the original result. Use q402_yield_posit…
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Human-readable decimal amount to withdraw, e.g. "100.00", or the literal "max" to withdraw the maximum currently redeemable (can be < full position under vault liquidity caps). |
| chain | string | – | Chain to withdraw on. 'bnb' (USDC or USDT) or 'base' (USDC only). The actual venue is reported in the receipt. |
| confirm | boolean | – | MUST be true to actually withdraw funds - set only after the user explicitly approved this exact withdrawal in chat. Omit (or false) to preview without moving funds. |
| consentToken | string | – | Two-phase consent token. Leave unset on the first call to get a preview + token; re-call with confirm:true AND this token after the user approves. Bound to (chain, token, amount, wallet). |
| idempotencyKey | string | – | Optional durable idempotency key. Omit and the tool generates a FRESH random key per invocation, so every call executes a distinct withdrawal. Pass your own STABLE key only for opt-in retry-safety -… |
| protocol | string | – | Venue to withdraw from when the wallet holds the same token in more than one lending venue on a chain. Omit when unambiguous; on an "AMBIGUOUS_POSITION" error re-call with one of the `protocols` the… |
| token | string | yes | Stablecoin to withdraw. USDC or USDT on bnb; USDC only on base. |
| walletId | string | – | Optional Agent Wallet address to withdraw to when the owner holds multiple wallets. Defaults to Q402_AGENT_WALLET_ADDRESS env, then the owner's default wallet on the server. |
No output schema declared.
No examples provided.
How do I install the io.github.quackai-org/q402-mcp server?
io.github.quackai-org/q402-mcp runs locally as an npm package, launched with npx -y @quackai/q402-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @quackai/q402-mcp
claude mcp add quackai-org-q402-mcp -- npx -y @quackai/q402-mcp
What is the io.github.quackai-org/q402-mcp server?
io.github.quackai-org/q402-mcp is listed in the public MCP registry as io.github.quackai-org/q402-mcp. Q402 - gasless payments, yield, escrow, bridge & NAV triggers on 12 EVM chains. Sandbox-default. This page covers its npm package (@quackai/q402-mcp).
Is the io.github.quackai-org/q402-mcp server safe to use?
io.github.quackai-org/q402-mcp scores 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.quackai-org/q402-mcp server expose?
io.github.quackai-org/q402-mcp exposes 52 tools: q402_doctor, q402_quote, q402_balance, q402_pay, q402_batch_pay, and 47 more. Their descriptions and schemas cost roughly 17,992 tokens of context every time the server is loaded.
Is the io.github.quackai-org/q402-mcp server still maintained?
io.github.quackai-org/q402-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.quackai-org/q402-mcp server under?
io.github.quackai-org/q402-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.