All servers / Security / Verify402 MCP server
Verify402 MCP server
MCP server for verify402: a free, fail-closed preflight gate before signing, plus five paid on-chain checks paid per call via x402.
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 1.1.7. Package: verify402-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (10.1 seconds including download)
- Tools offered: 3
- Last published: 2026-11-18
- Weekly downloads (npm): 780
- License: Apache-2.0 · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
preflight_gate9 of 9 parameters describedCall 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. Optional caller-supplied checks: policy.sellerPayoutWallets is a payout allowlist, not provenance; policy.sellerPayoutManifest fetches a seller-signed manifest from a caller-pinned HTTPS origin and is the only source of payee_payout_binding; policy.obligation checks a local settled-key ledger and cumulative spend against a grant. The gate does not persist either state.
inspect_4025 of 5 parameters describedRead an x402 402 challenge BEFORE paying it. Pass a public endpoint URL (or the challenge you already have) and get back the price, token, network, payee, the bound resource, and a PASS / CAUTION / BLOCK verdict with typed reasons and a receipt. Use this when an agent is about to pay a server you do not control. The service fetches the challenge once, read-only: it never signs, pays, or settles. A recognized dollar stable (USDC, USDT, DAI, USDG) is named; a volatile asset gets a caution because it cannot be priced in USD. Free.
directory_402no parametersList the public x402 endpoints verify402 watches, with the price, network, payee, a protocol verdict (is the challenge well-formed?) and a sign verdict (should an agent sign it?), plus any changes since the previous check. Use it to see what the ecosystem is asking for before wiring an agent to it. Free.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.