What does this scorecard check?

It combines the public evidence available for a live x402 endpoint, a public GitHub repository, and an MCP Registry record or remote. It checks readiness signals and launch metadata; it does not certify safety, ranking, traffic, or future behavior.

Does Ontario publish my MCP server or endpoint?

No. The scorecard is diagnostic. You remain responsible for publishing the endpoint, MCP Registry record, repository metadata, and any third-party catalog submissions.

Do I need to send a wallet or API key?

No. This free check uses public HTTPS URLs only. It does not request private keys, seed phrases, credentials, payment headers, private repositories, or tool calls.

Free MCP marketplace listing checker · x402 launch checklist

Find the launch blocker before agents discover or pay.

In about two minutes, check the public contract that MCP registries, marketplaces, crawlers, and agent buyers can see: live x402 HTTP 402 behavior, MCP Registry metadata and handshake evidence, GitHub launch files, and the links that make your service legible.

Run the free 2-minute check Diagnose zero agent buyers Check Bazaar activation Price an endpoint Generate launch artifacts See the $49 publish pilot

One score one public report and one next fixPublic URLs only no credentialsNo wallet no payment signatureNo certification evidence, not a guarantee

Run the free launch check

Start with one public URL. Add the other surfaces for a marketplace-ready view.

The check may fetch public metadata, but it does not echo fetched source, send credentials, sign payments, or invoke MCP tools.

What you get: a score, a public report URL, a README badge, and the first fix worth doing to make the result discoverable before asking agents to pay.

Your launch decision appears here

Run one public check to find the highest-impact gap across endpoint, registry, repository, and remote evidence.

For endpoint providers

See whether price, network, manifest, HTTP 402 behavior, OpenAPI, and public evidence agree before you ask agents to spend.

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