Call the read-only MCP JSON-RPC endpoint
Changed onRead-only public MCP endpoint. No API key or OAuth required. Clients must inspect JSON-RPC error even on HTTP 200. Legacy batches are accepted with no transport header or version 2025-06-18; use individual requests for newer transports. Notifications return HTTP 202 without a body. The selected MCP-Protocol-Version controls the wire contract; see /api-policy.md.
Request
- Base URLhttps://thorchain.org
- Authnone required
Headers
MCP transport version. Classic clients may omit it during initialize and negotiate through params.protocolVersion. Modern stateless requests must use 2026-07-28 and include matching io.modelcontextprotocol/protocolVersion metadata plus Mcp-Method (and Mcp-Name for named operations). Unsupported operational header versions are rejected with a typed 400 error. See /api-policy.md.
Required for modern stateless transport; must equal the JSON-RPC method.
Required for modern tools/call and resources/read; must match params.name or params.uri. Non-ASCII values may use the MCP base64 header encoding.
Request body
Response
JSON-RPC result or typed application error. Legacy batches return an array.
Changes
- breaking
added required request body
- info
added the new optional
headerrequest parameterMCP-Protocol-Version - info
added the new optional
headerrequest parameterMcp-Method - info
added the new optional
headerrequest parameterMcp-Name - info
added the media type
application/jsonfor the response with the status - info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the non-success response with the status
- breaking
- breaking
removed the success response with the status
- info
added the success response with the status
- breaking