@quackai/q402-mcp
npm
v0.11.25
Source verified
Published by quackai-org — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for Q402. Gasless USDC/USDT/RLUSD/Q payments on 12 EVM chains (USDG on Robinhood Chain), Q402 Yield (gasless supply and withdraw into Aave, Lista, and Morpho lending vaults), gasless non-custodial escrow (create, fund, release, refund, dispute)
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Untrusted-input tools ([q402_agent_spend_report]) co-exist with external-action tools ([q402_request_create, q402_redstone_trigger_create]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [q402_agent_spend_report] → sinks [q402_request_create, q402_redstone_trigger_create]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow q402_agent_spend_report → q402_request_create
Each tool and what it can reach — statically extracted from the published source.
q402_agent_spend_reportingests untrusted inputq402_redstone_trigger_createnetwork egressq402_request_createnetwork egressq402_agentic_infono sensitive capabilityq402_balanceno sensitive capabilityq402_batch_payno sensitive capabilityq402_bridge_gas_tankno sensitive capabilityq402_bridge_historyno sensitive capabilityq402_bridge_quoteno sensitive capabilityq402_bridge_sendno sensitive capabilityq402_clear_delegationno sensitive capabilityq402_doctorno sensitive capabilityq402_escrow_createno sensitive capabilityq402_escrow_disputeno sensitive capabilityq402_escrow_lockno sensitive capabilityq402_escrow_refundno sensitive capabilityq402_escrow_releaseno sensitive capabilityq402_escrow_statusno sensitive capabilityq402_memory_summaryno sensitive capabilityq402_oft_historyno sensitive capabilityq402_oft_quoteno sensitive capabilityq402_oft_sendno sensitive capabilityq402_quoteno sensitive capabilityq402_receiptno sensitive capabilityq402_recurring_cancelno sensitive capabilityq402_recurring_createno sensitive capabilityq402_recurring_firesno sensitive capabilityq402_recurring_listno sensitive capabilityq402_recurring_pauseno sensitive capabilityq402_recurring_resumeno sensitive capabilityq402_recurring_skip_nextno sensitive capabilityq402_redstone_feedsno sensitive capabilityq402_redstone_trigger_cancelno sensitive capabilityq402_redstone_trigger_listno sensitive capabilityq402_request_payno sensitive capabilityq402_request_statusno sensitive capabilityq402_stakeno sensitive capabilityq402_stake_positionsno sensitive capabilityq402_unstakeno sensitive capabilityq402_vendor_historyno sensitive capabilityq402_wallet_statusno sensitive capabilityq402_yield_depositno sensitive capabilityq402_yield_positionsno sensitive capabilityq402_yield_reservesno sensitive capabilityq402_yield_withdrawno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.11.25 latest |
A 97/100 | 1 | 1.13.0 | 2026-09-07 |
v0.11.24 |
A 96/100 | 1 | 1.13.0 | 2026-09-04 |
v0.11.23 |
A 96/100 | 2 | 1.13.0 | 2026-08-27 |
v0.11.22 |
A 96/100 | 2 | 1.12.1 | 2026-08-19 |
v0.11.19 |
A 96/100 | 2 | 1.12.1 | 2026-08-18 |
v0.11.17 |
A 96/100 | 2 | 1.12.1 | 2026-08-16 |
v0.11.16 |
A 96/100 | 0 | 1.12.1 | 2026-08-13 |
v0.11.15 |
A 96/100 | 0 | 1.12.1 | 2026-08-06 |
v0.11.12 |
A 96/100 | 0 | 1.12.1 | 2026-07-31 |
v0.11.11 |
A 100/100 | 0 | 1.5.0 | 2026-07-22 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @quackai/q402-mcp --online
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.