verify402
NPM · VERIFY402-MCP
Free x402 preflight gate plus paid on-chain truth checks for AI agents.
Available components
Last scanned (14 hours ago)
Scores higher than 36% 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 Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 336 tokens (~336/item across 1 items; 1 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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.
- 22 Oct 26 −11
- Stability: 0.07 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 293 → 336 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.89 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 1.0.3 → 1.0.5 functional
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 +1
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.0.2 → 1.0.3 functional
- 19 Oct 26 54
First indexed and scored.
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 22 Oct 2026 · Analysed npm/verify402-mcp@1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
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 →
preflight_gate ~336
Call this BEFORE signing any crypto transaction or x402 payment request. Returns PASS / CAUTION / BLOCK with typed reasons, the checks that actually ran, the checks that did not, and a short-lived receipt bound to the exact intent + block. If sign_allowed is false, DO NOT SIGN. If requires_ack is true, surface the reasons to the operator before signing. The receipt expires (default 90s): call again rather than reuse it. Free. Pass `from` (the wallet that will sign) to enable simulation and balance checks. For kind=transaction, chainId is REQUIRED (400 missing_chain without it). For payment intents with no `from` or no proof, the response is PASS with structural_only:true and names what was not checked.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | EVM chain id: 1 Ethereum, 42161 Arbitrum, 8453 Base. For payment, cross-checks the network. |
| data | string | – | 0x calldata for the transaction |
| from | string | – | The wallet that will sign. Strongly recommended: enables simulation and balance checks. |
| kind | string | yes | payment = an x402 402 challenge; transaction = a chain transaction |
| payment | object | – | Required when kind=payment |
| policy | object | – | Operator policy. Omit for structural checks only. |
| to | string | – | Transaction target (required when kind=transaction) |
| ttlSeconds | number | – | Receipt lifetime in seconds, 15-300 (default 90) |
| value | string | – | Native value in wei, as a decimal string |
No output schema declared.
No examples provided.
How do I install the verify402 MCP server?
verify402 runs locally as an npm package, launched with npx -y verify402-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 · verify402-mcp
claude mcp add a32116150-ctrl-verify402-mcp -- npx -y verify402-mcp
What is the verify402 MCP server?
verify402 is an MCP server listed in the public MCP registry as io.github.a32116150-ctrl/verify402-mcp. Free x402 preflight gate plus paid on-chain truth checks for AI agents. This page covers its npm package (verify402-mcp).
Is the verify402 MCP server safe to use?
verify402 scores 59 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 verify402 MCP server expose?
verify402 exposes 1 tool: preflight_gate. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.
Is the verify402 MCP server still maintained?
verify402 is still listed as active in the MCP registry. We last reached this channel on 22 October 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 verify402 MCP server under?
verify402 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.