verify[402]
snapshot · block — Run free check

MCP · stdio · free gate

Put the gate inside the bot.

One MCP server gives Claude Desktop, Cursor, OpenCode, or any agent the free preflight gate plus five paid on-chain checks. The free gate answers with a receipt; the paid checks settle per call over x402.

Official MCP Registry: see entry npm: verify402-mcp v1.1.2 Paid calls · Base Sepolia testnet Free gate · no wallet

The tool surface

One gate, five deep questions.

The gate is free because it has to run before every signature. The paid tools answer the questions that need a measurement at a pinned block.

ToolPriceQuestionWhat comes back
preflight_gatefreeShould I sign this payment or transaction?PASS / CAUTION / BLOCK, typed reasons, checked / notChecked, and a short-lived receipt
inspect_402freeWhat does this 402 actually ask for?Price, token, network, payee, the bound resource, and a PASS / CAUTION / BLOCK verdict from a read-only fetch
directory_402freeWhat is the ecosystem asking for right now?Watched public x402 endpoints with protocol and sign verdicts, plus recorded changes
verify_arbitrage$0.05Is this cross-venue arbitrage real, right now?Verdict + evidence + no_edge when there is none
check_token_safety$0.10Can this token be sold on the configured venues?TRUST / CAUTION / AVOID, live contract facts, liquidity, a quote-based sellability check
get_best_route$0.03What would the chain actually pay?Every quoted venue at one pinned block, best first
verify_quote_fairness$0.05Is this quote someone gave me honest?fair / overpaying / too_good_to_be_true, with the chain book
get_trade_depth$0.05How big can I trade before the round trip eats me?Per-size impact, round-trip cost, and the largest size under your tolerance

Paid calls are testnet USDC over x402 for the public demo. The bridge signs the payment only — it never signs or sends a trade — and it only pays a 402 from the configured server, on an allowlisted network, to the verify402 payee.

Install

Start with the free gate. Add the wallet later.

The npm package is published to the public registry, so you can run it directly with npx without cloning or building. The published version is 1.1.2. 1.1.2 carries one bridge fix: the installed payer forwards the challenge's extensions.bazaar into the payment payload, so a settlement can be cataloged. Paid calls in the public demo use Base Sepolia testnet USDC; mainnet settlement is not enabled by this release.

Mode 1 · no key

Free gate only.

Omit EVM_PRIVATE_KEY. The server registers only the free tools (preflight_gate, inspect_402, directory_402), and nothing can be charged. This is the safest way to try it.

Mode 2 · paid tools

A dedicated hot wallet.

For the public demo, add a wallet with Base Sepolia testnet USDC and set VERIFY402_NETWORKS=eip155:84532. MAX_PAYMENT_USD caps one payment at signature time; MAX_DAILY_USD caps the UTC day. Never use a main wallet. The analysis reads mainnet chain data, but payment is testnet-only; mainnet settlement is an explicit future deployment choice.

Run via npx · no wallet required

npx -y verify402-mcp --help

Official MCP Registry & npm Distribution

Published on npm as verify402-mcp (version 1.1.2). The official Model Context Protocol Registry lists the published entry as active. The repository source matches the published 1.1.2 package. Machine agents can also fetch the machine-readable service manifest and OpenAPI 3.1 specification.

verify402 MCP server

Client · Claude Desktop / Cursor

Paste one server block.

Claude Desktop uses claude_desktop_config.json; Cursor uses .cursor/mcp.json. This block is free-only. For paid tools, add EVM_PRIVATE_KEY, MAX_PAYMENT_USD and optionally MAX_DAILY_USD to env.

Free-only config

{
  "mcpServers": {
    "verify402": {
      "command": "npx",
      "args": [
        "-y",
        "verify402-mcp"
      ],
      "env": {
        "VERIFY402_URL": "https://vex402.online"
      }
    }
  }
}

Client · OpenCode V2

Servers live under mcp.servers.

Put this in opencode.jsonc or the global ~/.config/opencode/opencode.jsonc. For paid tools, use "EVM_PRIVATE_KEY": "{env:EVM_PRIVATE_KEY}" and export the key in the environment that starts OpenCode — do not write it into the file.

opencode.jsonc · free-only

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "verify402": {
        "type": "local",
        "command": [
          "npx",
          "-y",
          "verify402-mcp"
        ],
        "environment": {
          "VERIFY402_URL": "https://vex402.online"
        }
      }
    }
  }
}

V2 uses mcp.servers and disabled; there is no enabled field. The server name prefixes its tools in OpenCode.

Alternative install options

If you prefer a pinned npm version: npx -y verify402-mcp@1.1.2. From source: git clone https://github.com/a32116150-ctrl/verify402, then cd verify402/mcp-bridge && npm ci. The published npm tarball is https://registry.npmjs.org/verify402-mcp/-/verify402-mcp-1.1.2.tgz.

The honesty boundary

What it catches — and what it does not.

It checksIt does not
A swapped payee, a lookalike asset, a wrong amount, a bad network, an expired authorizationWhether the recipient is a scammer or a sanctioned address
Decoded calldata: transfers, approvals, permits, common V2/V3 swaps; unlimited approvals and spendersContract audits, proxy upgrades, owner privileges, or a token's intent
Contract bytecode, swap deadline, minimum output, output recipient, and an eth_call simulation from your walletFull balance-delta / state-change simulation; MEV and sandwich protection
The x402 payment itself: price, network, asset, payee, facilitator, before the caller signsCounterparty identity, tool metadata, hidden instructions in tool output, or off-chain promises: “the seller will deliver after you pay”
Receipt integrity: HMAC, intent hash, pinned block, expiryThe agent ignoring the tool, or a signer that does not verify the receipt

A PASS means the left column passed at that block. It is not a guarantee that a token is safe, a trade will profit, or a counterparty will deliver. It is not a counterparty audit and does not scan tool descriptions or responses for prompt injection. It catches a class of measurable signing mistakes — not every scam.

Enforcement, not advice

The MCP tool is advisory: it cannot stop an agent that ignores the answer. Use the reference executor to verify the receipt and refuse to call the signer without it. The full request shape is in /docs#preflight.

Why a package

Because a clone is friction.

An MCP server is only in the path if installing it is one line. npx runs a versioned package on first use, your client config stays small, and updates are a version bump — not a git pull. The package is distribution, not another endpoint.

Add the server

One block in Claude, Cursor, or OpenCode. No build, no clone, no submodule.

Call the gate

Free, no wallet. The agent gets PASS / CAUTION / BLOCK and a receipt bound to the intent and block.

Add paid depth

When the agent needs a measurement, the same server pays per call over x402. No subscription.

Install from the public npm registry with npx -y verify402-mcp@latest; the pinned npm version above is the reproducible alternative. Package name: verify402-mcp. License: Apache-2.0 — keep the copyright notice, license, and NOTICE file when redistributing. Source: mcp-bridge.