Does this checker invoke MCP tools?

No. Ontario checks public registry metadata and read-only initialize and tools/list responses. It does not invoke tools, send credentials, send payment headers, or certify safety.

Does a passing report mean the MCP server is safe?

No. The report is evidence about registry and observable MCP metadata. It is not an official registry certification, security audit, service-quality guarantee, or payment authorization.

MCP Registry evidence check

Make your MCP server easier for agents to choose.

Check the public registry record and a live MCP remote before agents select a tool. Ontario checks the metadata and read-only protocol surfaces that make a server legible; 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.

What this check answers

Can an agent identify it?

Namespace, title, description, version, and canonical HTTPS website are checked against the public record.

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, publish the record through the official registry workflow, then run Ontario’s free live x402 verifier. If a real production endpoint still needs implementation work, use the free launch kit or review the fixed-scope $199 Agent Catalog Launch Pack.