preflight402
This server provides a free, no-wallet trust check for x402 and MPP payment endpoints, returning a trust-preview.v1 verdict with a proceed/caution/avoid recommendation. Capabilities include:
Probing endpoint liveness, latency, and TLS validity.
Detecting 402 handshakes (x402 v1/v2, MPP).
Sanity-checking pricing and providing USD estimates.
Checking ERC-8004 on-chain identity binding.
Scoring reputation with Sybil filtering to eliminate fake reviews.
Offering paid-tier fields like uptime history (stubbed on free tier). It requires no authentication and can be used as an MCP tool, REST API, or integrated via the preflight402-guard library for automatic preflighting with identity checks and price limits.
Provides on-chain reputation verification on Solana (SVM) to assess trustworthiness and Sybil-filtered reputation of payment endpoints.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@preflight402 preflight https://api.example.com/paid before paying"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
preflight402
One free call before your agent pays. Health, authenticity, and Sybil-filtered reputation — one verdict.
A free trust/health preflight for the agent payment economy (x402). It probes
an endpoint before your agent pays and returns one trust-preview.v1 verdict:
liveness, TLS, the 402 handshake (x402 v1/v2 + MPP detection), price sanity,
continuous uptime history, ERC-8004 identity binding, and Sybil-filtered
on-chain reputation — rolled into a proceed / caution / avoid recommendation
with plain-language reasons. No wallet, no key, no charge.
Why filtered reputation matters: one live agent shows a 99.8/100 average from 996 reviewers — until Sybil filtering collapses those reviewers into 12 independent funding clusters at 89.7. Raw reputation is trivially farmed; this is what the verdict actually scores. (Separately, only ~4% of x402 payees bind to any ERC-8004 identity at all — so most verdicts run on health, price, and handshake, and say so honestly.)
Why "listed" means little: across 7.76M probes over 15 days of a 51,331-endpoint catalog, two squatting hosts account for 58% of every listed x402 endpoint — one serving a uniform 404 behind a "This app isn't live yet" placeholder, the other a uniform Cloudflare TLS failure. Strip them out and 87% of real endpoints work; measured per provider, about one host in seven (13.9%) serves no valid 402. Read the findings: What 7.8M probes say about the x402 economy — including why a GET-only crawl (ours included, before we fixed it) overstates x402 invalidity ~2×. Full method and caveats: docs/checkpoint-m3.md.
30-second quickstart
Point any agent at the hosted MCP endpoint — no wallet, no key, no install:
https://preflight402.ironshell.io/mcpOr check an endpoint over plain HTTP:
curl 'https://preflight402.ironshell.io/preflight?url=https://api.example.com/paid'Related MCP server: Agent Identity MCP Server
Guard every payment automatically
preflight402-guard turns the service into a payment gate for the
x402 Python SDK — safety becomes
default-on instead of something an agent has to remember to call:
pip install "preflight402-guard[x402]" # PyPI publish pending; for now: pip install "git+https://github.com/duskwire/preflight402.git#subdirectory=guard"from preflight402_guard import Guard
from x402 import x402Client
guard = Guard() # block "avoid", warn on "caution"
client = x402Client()
guard.install(client) # every payment is preflighted before signing;
# a bad verdict raises PaymentAbortedErrorIt also cross-checks that the payee your client selected matches the endpoint
that was preflighted (the 402's resource URL is attacker-controlled), enforces
an optional max_price_usd ceiling against the actual selected terms, and
fails open by default so your commerce never depends on our uptime. There's
a CLI too: preflight402-guard check <url>. See guard/README.md.
Status
Live at preflight402.ironshell.io and in
the official MCP registry as
io.ironshell/preflight402. The free preflight engine (health + 402 parse +
verdict), continuous probing with uptime history, ERC-8004 binding, and the
Sybil filter are all shipped and serving live. The whole service is free —
there is no paywall.
Use it
As an MCP tool (no wallet, no key)
The preflight tool takes a url and returns a trust-preview.v1 verdict.
Easiest — point any MCP client at the hosted instance, no install:
https://preflight402.ironshell.io/mcp (streamable-http)Or run it yourself over stdio. Claude Code — one line (PyPI publish pending;
until then point --directory at a clone):
claude mcp add preflight402 -- uvx --from preflight402 preflight402-mcp
# pre-PyPI: claude mcp add preflight402 -- uv run --directory /path/to/preflight402 preflight402-mcpClaude Desktop — add to claude_desktop_config.json:
{
"mcpServers": {
"preflight402": {
"command": "uvx",
"args": ["--from", "preflight402", "preflight402-mcp"]
}
}
}Either way, run it as a hosted HTTP server with
preflight402-mcp --transport streamable-http (serves the same tool at
http://<host>:8000/mcp).
As a REST call
The hosted instance also serves REST:
curl 'https://preflight402.ironshell.io/preflight?url=https://api.example.com/paid'Or run it yourself (serves REST + MCP on one port):
uv run uvicorn preflight402.api.app:app --port 8402
curl 'http://localhost:8402/preflight?url=https://api.example.com/paid'Development
Requires uv.
uv sync # create venv + install deps
uv run uvicorn preflight402.api.rest:app # serve on :8000
curl http://localhost:8000/healthz # {"status":"ok","version":"0.1.0"}
uv run pytest # tests
uv run ruff check . # lint
uv run ruff format --check . # formattingLayout
src/preflight402/
├── api/ # REST + MCP server
├── probe/ # async prober, TLS inspection, 402 parsers (x402 v1/v2, MPP)
├── verdict/ # rules -> trust-preview.v1 JSON
├── chains/ # ChainVerifier interface: EVM (Base), SVM (Solana)
├── reputation/ # ERC-8004 subgraph client, endpoint binding, Sybil filter
├── ingest/ # endpoint seed ingesters (Bazaar, x402scan, ...)
├── scheduler/ # probe loop with per-host politeness
└── db/ # SQLite (WAL) schema + queries
guard/ # preflight402-guard: client-side auto-preflight for the x402 SDK
tests/ # unit/ + golden/ (captured 402 responses) + integration/ (marked slow)
deploy/ # Dockerfile + deploy notes
docs/ # trust-preview.v1 schema + API docs (M8)Available Tools
1 toolpreflightx402 Preflight Trust CheckAInspect
One free call before your agent pays.
Probes the URL (no wallet, payment, or auth) and returns a
trust-preview.v1 verdict: liveness and latency, TLS validity, the 402
payment handshake with protocol detection (x402 v1/v2, MPP-capable),
detected networks/asset/price with a USD estimate, ERC-8004 identity
binding with Sybil-filtered reputation for the payee (which can adjust
the recommendation), and a proceed / caution / avoid recommendation with
human-readable reasons. Paid-tier fields (uptime history, reseller
analysis) are present but null on the free tier.
Inputs: url (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool available, there is no possibility of confusion between tools. The tool's purpose is clearly defined as a URL preflight check.
The single tool name 'preflight' is clear and appropriate for its function, and with only one tool, there is no inconsistency to evaluate.
A single tool is on the low end of the scale, suggesting a thin server. However, the tool is comprehensive and well-scoped to the server's stated purpose of preflight checks, making it borderline.
The preflight tool covers all essential aspects of the intended function: probing URLs, checking liveness/TLS, payment handshake, network detection, identity, and recommendation. No obvious gaps exist within the preflight domain.
Maintenance
Related MCP Connectors
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
Independent trust scores, tool surfaces and change history for MCP servers.
Crypto transaction firewall and risk tools for MCP agents.
Trust, freshness, policy, and discovery layer for public MCP servers.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server exposing AgentForge Trust Score audit tools. Query trust, evaluate policies, list trusted servers, recommend with filter.423 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.48 PyPIMIT
- FlicenseAqualityCmaintenanceReputation and trust scoring service for AI agents, exposed as an MCP server. Evaluate counterparties, report interactions, issue portable trust certificates, and detect Sybil attacks.2383 PyPI-

acuris-agent-guardofficial
AlicenseNot gradedqualityCmaintenanceMCP server that verifies storefront merchants before AI agents make payments, checking if the merchant is a real legal entity bound to the domain, and returning a PROCEED, ABORT, or REVIEW decision to prevent payment to clones or fraudulent stores.MIT