For endpoint providers
See whether price, network, manifest, HTTP 402 behavior, OpenAPI, and public evidence agree before you ask agents to spend.
Know whether agents can discover and call your paid endpoint.
Combine the public signals that matter at launch: live x402 HTTP 402 behavior, MCP Registry metadata and read-only handshake evidence, and the public repository files agents and registries use to understand your service.
Public URLs onlyNo wallet no payment signatureNo tool calls read-only checksNo certification evidence, not a guarantee
Run the scorecard
Provide any one public target. Add all three for the clearest launch picture.
The check may fetch public metadata, but it does not echo fetched source, send credentials, sign payments, or invoke MCP tools.
Your score appears here
Run one public check to get a weighted launch score and the next fix worth doing.
-/100
Next action
Share the evidence
The badge is a point-in-time public scorecard signal, not a safety certification. Paste this in your GitHub README or docs page to link agents back to the report.
For MCP builders
Check the official Registry record, remote transport, initialize handshake, tools/list contract, and x402 discovery surfaces.
For teams shipping from GitHub
Find missing tests, manifests, docs, CI evidence, and sensitive-looking filenames without returning repository source.
Evidence boundary
This scorecard helps a provider find public launch blockers. It does not guarantee agent traffic, search ranking, endpoint safety, settlement success, or future behavior. Publishing and third-party registry submission remain operator-controlled.
What Ontario checks · What Ontario does not check · Commercial scope and billing boundary