Ontario Protocol MCP server

• Registry namecom.ontarioprotocol/ontario-protocolverified in the MCP registry

The registry name sits under ontarioprotocol.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools17
• Server calls itselfontario-protocol
• Server version1.0.12
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 97 ms.

• Its tools do every use case we checked: check a paid endpoint's x402 payment readiness before listing; find the first blocker stopping agents from paying; compare endpoint readiness against an agent spend policy.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer110 ms
• Space in an agent's context≈ 6,937 tokensthe definitions of all its tools (20), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results20 of 20 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• ontario_purchase_router

  Free deterministic pre-purchase routing across Ontario tools. Use this before any paid Ontario tool to decide whether the task is free-only, needs free preflight, or is eligible for a paid result after wallet, Base network, and explicit…

• ontario_task_fit

  Free task-to-tool matching with an optional Jev second opinion. With allow_typesafe=true, your public task and Ontario's public tool descriptions are sent to TypeSafe for Jev inference. Do not supply secrets, personal data, private URLs…

• agent_can_pay

  Free pre-payment policy decision. Agents ask whether an x402 endpoint should be paid under strict, standard, or permissive policy. The free result is sufficient by default; set require_audit_receipt only when a settlement-backed receipt…

• x402_readiness_verify

  Free check for whether a paid endpoint is ready for agent discovery and x402 payment. Returns a free end-to-end buyer-path diagnostic handoff plus a grade-aware provider handoff: validate listing metadata free before any optional 0.50…

• bazaar_buyer_intent_gap

  Free read-only provider audit that runs Coinbase's indexing preflight and measures one public x402 endpoint across five live CDP Bazaar buyer-search variations. Returns retrieval coverage, observed sample ranks, alternatives, public…

• find_x402_tool

  Free buyer-side search across Ontario's fresh strict-ready paid profiles, Agentic Market, and Coinbase CDP Bazaar. Rank public, credential-free endpoint candidates by task relevance plus bounded source-reported recent activity, with…

• ontario_find-api

  Which x402 API should I call for this task? Returns up to 5 paid APIs from Coinbase Bazaar and Agentic Market that answered a fresh unpaid probe with a valid Base USDC payment challenge at their listed price, ranked by repeat buyers…

• x402_launch_kit

  Generate a validated listing payload, x402 resource draft, MCP descriptor, GitHub readiness workflow, README snippet, and registry copy for one paid endpoint.

• ontario_validate-service

  Free provider listing preflight. Validate public service metadata before buying the 0.50 USDC Ontario launch passport. Returns field errors or a normalized request and publication decision. Set verify_now only to create a public readiness…

• ontario_list-service

  Publish a provider-owned x402 API so AI agents can discover and buy it. After free validation and a Bazaar buyer-intent audit, the 0.50 USDC Launch Passport creates a signed public HTML/JSON profile, readiness and Coinbase indexing…

• ontario_refresh-listing

  Use only for an existing paid Ontario provider profile when the caller wants a fresh live readiness observation attached to its canonical HTML, JSON twin, and badge. This tool cannot edit provider metadata, improve a grade by payment, or…

• agent_trust_preview

  Free live, rate-limited agent trust preview for one public endpoint. Returns safe signals and issues without the paid evidence bundle or attestation; use the paid trust scan only when the preview is insufficient.

• github_x402_repo_scan

  Free pre-deployment scan of one public GitHub repository for x402 implementation, HTTP 402 tests, payment configuration, buyer documentation, discovery metadata, CI gates, and sensitive filenames. Returns paths and remediation, never…

• ontario_list-agent

  Use only when the caller owns the agent and wants to submit a public directory listing. Validate the payload for free first; payment does not guarantee approval, traffic, ranking, or safety. Agent payment guidance: run free can-pay and…

• ontario_validate-agent

  Validate an agent listing payload for free before publication. Never publishes, signs or spends.

• ontario_validate-refresh

  Check an existing paid provider profile's refresh eligibility for free, including cooldown. Never refreshes, signs or spends.

• x402_verification_reports

  Public ledger of recent x402 readiness reports.