CLI
One command against any endpoint. Deterministic PASS/FAIL, exact failing step, JSON or markdown output.
CLI guidemcpreflight runs the MCP initialize handshake and tools/list validation against any endpoint. No tools invoked, no credentials, no payments. Then it tells you exactly what passed and what didn't.
Same engine, same read-only guarantees, wherever you need it.
One command against any endpoint. Deterministic PASS/FAIL, exact failing step, JSON or markdown output.
CLI guidemcp-trust-check on every pull request. Fails the build when a registered server stops completing a clean handshake.
Expose schema_check and x402_inspect as MCP tools inside your own agent stack.
Every check is reproducible with one command and documented with its limits.
initialize + tools/list, tool names, descriptions, input/output JSON schemas, required fields. 46,216 property-level findings logged across the registry.
Schema guideHTTP 402 challenge shape, payment documents, accepts[], discovery manifests, latency and response digest, all without paying.
x402 guidePer-server reports, status badges and JSON APIs for 9,991 official-registry endpoints. Re-scanned every Monday.
Browse directoryERC-8004 on-chain registrations cross-checked against their declared MCP endpoints: 40 endpoints, five-level verdicts, reasons and timestamps.
Sample reportOf 9,991 remote endpoints in the official registry. Plus a second finding: all 213 Smithery-registered entries refused anonymous handshakes. Full report, method and limits →
Honest limits. mcpreflight never calls MCP tools, accepts credentials, executes server commands, signs or settles payments, or proves delivery. PASS is a deterministic observed-check result for the checks in that version — not a security certification and not a trust score.