Can an agent identify it?
Namespace, title, description, version, and canonical HTTPS website are checked against the public record.
MCP server registry check
Check MCP Registry readiness before agents choose your server.
Validate the public registry record, server.json identity, and a live MCP remote before agents select a tool. Ontario checks read-only protocol surfaces; it does not invoke tools or authorize payment.
Free, read-only, and credentialless. A report is evidence about observable behavior, not official registry certification or a safety guarantee.
Run the free check
Use a direct MCP Registry server JSON URL, a live MCP remote, or both. For a search URL with multiple results, add the exact server name.
The checker sends only read-only metadata requests. It never sends Authorization, payment, or tool-call payloads.
Report appears here
Run the check to see score, grade, evidence, and exact remediation steps.
0/100
Next action
Get a free publish-or-fix decision
Send the same public MCP URL and a work email. Ontario will return a scope decision before any paid work; no payment, wallet credentials, or subscription is created.
What this check answers
Can an agent reach it?
Ontario sends read-only initialize and tools/list JSON-RPC requests. It does not invoke a tool.
Can an agent understand payment context?
When present, /.well-known/mcp.json and /.well-known/x402.json are detected. Payment still requires an independent preflight.
After the report
Fix the blocking metadata, then run Ontario's free five-search Bazaar audit. If the public remote is ready and the retrieval evidence is useful, review the MCP + x402 Agent Tool Procurement Passport, then publish it through the existing 0.50 USDC launch passport. Payment buys Ontario evidence processing and publication, not registry or Bazaar placement, ordering, traffic, buyers, or revenue.