Read-only diagnostics for AI agents and Web3 payments. Every command answers one question with PASS / FAIL / UNKNOWN — and documents what it does not cover.
Is your MCP/x402 endpoint discoverable and understandable by an agent? Checks HTTP 402 payment documents, MCP initialize, tools/list, tool name / description / inputSchema / required fields.
What does an x402 endpoint demand before serving? Parses HTTP 402 payment documents: scheme, network (CAIP-2), asset, amount, payTo — plus response latency and SHA-256 evidence. Never pays.
Does your MCP server advertise OAuth metadata an agent can actually discover? 401 challenge, WWW-Authenticate resource_metadata, Protected Resource Metadata, authorization server metadata, PKCE S256.
Solana transaction evidence from one public RPC: slot, block time, execution error, parsed instructions, fee, response hash. If the RPC cannot see a transaction it says UNKNOWN — never "does not exist".
Normalizes operator-supplied cross-chain message status JSON (source/destination/delivered/failed) into a conservative evidence report. Missing fields stay UNKNOWN. Protocol APIs are the roadmap.
On-chain delivery receipts for x402 on Solana: payment → delivery → SHA-256 digest anchored to a public PDA → anyone can verify independently. The evidence adapter beneath this suite.