mcpbeat

Ontario Protocol MCP Server

com.ontarioprotocol/ontario-protocol
answering

Ontario Protocol is answering right now. Last checked 13 min ago. It exposes 8 tools.

Verify x402 endpoints before payment or publish service profiles for agent discovery.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
256 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add ontario-protocol --transport http https://ontarioprotocol.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ontario-protocol": {
      "url": "https://ontarioprotocol.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ontario-protocol]
url = "https://ontarioprotocol.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ontario-protocol": {
      "url": "https://ontarioprotocol.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ontario-protocol": {
      "url": "https://ontarioprotocol.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ontario
ontario_agent-pay-query-v2
Live x402 endpoint readiness check before payment. This x402 paid API verification service helps verify an x402 endpoint before an AI agent pays: probe one public paid API and inspect the HTTP 402 challenge, payTo address, price, Base USDC network and asset, manifest freshness, buyer budget, and spend policy. Returns ALLOW or DENY with reasons, readiness score, report ID, settlement metadata, and a settlement-backed SHA-256 evidence receipt. Run free can-pay and readiness checks first. Readiness evidence is not a safety guarantee. Agent payment guidance: run free can-pay and readiness checks first; pay only when policy allows base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and 0.002 USDC is inside the agent budget. [PAID: 0.002 USDC via x402 on Base. Two-step flow: call without _x402_payment to receive the x402 payment requirements, then call again with _x402_payment set to a base64 x402 PaymentPayload to settle and receive the result.]
ontario_list-service
Use only when the caller owns an x402 endpoint and wants a public provider profile, live readiness scan, evidence link, and conditional fresh ready-grade eligibility in strict /discover and Ontario's task-to-tool buyer search, with a privacy-safe 30-day profile request receipt. A paid profile supersedes an older free preview for the same endpoint and method in public catalogs. Validate and run readiness first; payment does not guarantee a ready grade, traffic, ranking, purchases, or safety. Agent payment guidance: run free can-pay and readiness checks first; pay only when policy allows base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and 0.50 USDC is inside the agent budget. [PAID: 0.50 USDC via x402 on Base. Two-step flow: call without _x402_payment to receive the x402 payment requirements, then call again with _x402_payment set to a base64 x402 PaymentPayload to settle and receive the result.]
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 budget gates. Natural endpoint-verification tasks route to the free readiness verifier and disclose the optional 0.002 USDC settlement-backed receipt only when extra audit evidence is needed. Provider jobs such as publishing, registering, or making an x402 endpoint discoverable can route to the self-serve 0.50 USDC publication product after preflight. This tool never invokes another tool, signs a payload, or spends funds.
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 buy ranking or traffic. Agent payment guidance: run free can-pay and readiness checks first; pay only when policy allows base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and 0.10 USDC is inside the agent budget. [PAID: 0.10 USDC via x402 on Base. Two-step flow: call without _x402_payment to receive the x402 payment requirements, then call again with _x402_payment set to a base64 x402 PaymentPayload to settle and receive the result.]
x402
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 optional Base/USDC budget filtering. Paid Ontario publication adds no ranking score. This is discovery, not a safety certification; run readiness and can-pay before spending. When the query is provider-side publication intent, skip buyer marketplace search and return the free listing validator followed by the gated 0.50 USDC publication workflow.
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.
x402_readiness_verify
Free check for whether a paid endpoint is ready for agent discovery and x402 payment. Returns a grade-aware provider handoff: validate listing metadata free before any optional 0.50 USDC publication, and do not pay for publication while the endpoint is not ready-grade.
agent
agent_can_pay
Free pre-payment policy decision. Agents ask whether an x402 endpoint should be paid under strict, standard, or permissive policy.

Endpoints

URLTransportStateLatencyChecked
https://ontarioprotocol.com/mcp streamable-http answering 259 ms 13 min ago

Ontario Protocol — questions

Answers built from our own checks of this server.

What can Ontario Protocol do?
It exposes 8 tools, read directly from the server on our last check. Among them: agent_can_pay, find_x402_tool, ontario_agent-pay-query-v2, ontario_list-service, ontario_purchase_router, ontario_refresh-listing and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Ontario Protocol mostly used for?
Its tools cluster around ontario and x402. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Ontario Protocol working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 256 ms. The bar chart above shows every period we have measured.
Is Ontario Protocol still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Ontario Protocol?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Ontario Protocol need an API key?
No. Ontario Protocol completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Ontario Protocol?
It answers our handshake in 256 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.