Submit Tool or Service for Verification

Add your payment-gated HTTP API (x402) or Model Context Protocol (MCP) server to the live trust catalog. Verification starts immediately after email confirmation.

For MCP: must support Streamable HTTP or SSE. For x402: must challenge with HTTP 402.
We'll send a one-time magic link to confirm ownership and issue re-audit alerts.

The 9-Point Verification Checklist:

  • reach — Live HTTP accessibility and TLS handshake
  • challenge — Valid 402 response and PAYMENT-REQUIRED header (x402)
  • price_match — Actual billed price matches catalog claims
  • payto_match — Cryptographic recipient verification (no substitution)
  • mcp_list — Valid JSON-RPC tools and input schemas (MCP)
  • injection — Automated prompt injection & agent hijacking scan
  • paid_call — Real on-chain micropayment verification (Base Sepolia / Mainnet)
  • schema_match — Response strictly validates against promised output schema
  • canary — Canary secret tracking for unauthorized data exfiltration