Ontario Protocol MCP server
{
"mcpServers": {
"ontario-protocol": {
"type": "http",
"url": "https://ontarioprotocol.com/mcp"
}
}
}{
"mcpServers": {
"ontario-protocol": {
"type": "http",
"url": "https://ontarioprotocol.com/mcp"
}
}
}{
"mcpServers": {
"ontario-protocol": {
"type": "http",
"url": "https://ontarioprotocol.com/mcp"
}
}
}{
"servers": {
"ontario-protocol": {
"type": "http",
"url": "https://ontarioprotocol.com/mcp"
}
}
}{
"mcpServers": {
"ontario-protocol": {
"type": "http",
"url": "https://ontarioprotocol.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.6
What it does
Ontario Protocol exposes tools for x402 API providers to audit their discoverability in Coinbase Bazaar, verify endpoint readiness, and publish signed provider profiles. It is for API providers preparing to launch or agent builders checking endpoints before purchase.
- Run a free buyer-discovery audit to identify why an x402 API is not discoverable or callable by agents.
- Validate and publish a signed provider profile with readiness evidence and Bazaar retrieval snapshots for 0.50 USDC.
- Check whether a proposed payment passes local policy before an agent attempts to call a paid x402 endpoint.
Tools this server exposes
| Tool | Does |
|---|---|
| bazaar_buyer_intent_gap | Diagnose retrieval gaps across five buyer queries against an x402 endpoint. |
| x402_readiness_verify | Inspect whether an x402 endpoint is ready for buyer discovery. |
| agent_can_pay | Decide whether a proposed spend passes the agent's local spend policy. |
| find_x402_tool | Find task-relevant paid API candidates in Coinbase Bazaar. |
| ontario_validate-service | Validate provider publication inputs such as service name, description, endpoint, and per-call price. |
| ontario_list-service | Publish a signed provider launch profile with readiness evidence and Bazaar snapshot for 0.50 USDC on Base. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.