Skip to main content
GET
cURL
An authenticated GET returns 405 Method Not Allowed with Allow: POST. 0xinsider’s remote MCP server sends no notifications or server-to-client stream. Send JSON-RPC requests through Remote MCP using POST.

Headers

A GET reads no other header. MCP-Protocol-Version and Mcp-Session-Id are ignored here.

Response

The 405 is the expected answer, not a failure. A conforming client, the reference @modelcontextprotocol/sdk included, reads it as “no stream at this endpoint” and does not ask again. Until September 22, 2026 the same GET answered 200 with text/event-stream and closed the body at once, which clients treated as a dropped connection and reopened about once a second.

Example

What it does not return

  • A stream. The body is one JSON error object, not text/event-stream.
  • A tool result. Read that from the POST response.
  • A notification. The server sends none, which is why this method returns 405.
  • An answer for a key in ?token=. That returns 401 with error.reason api_key_in_query, the same as POST.
  • A public handshake. initialize, ping, and tools/list need no credential, but they are POST methods, and this GET always needs one.

Authorizations

Authorization
string
header
required

Legacy default or named integration API key, or OAuth 2.1 access token, in the Authorization header as Bearer oxi_sk_live_... or Bearer oxi_at_.... Default keys retain full access; integration keys are limited to their approved read, webhooks, export and usage scopes and expire within 90 days. All credentials share the owner's account limits. Data calls require an active Pro subscription and return live data. A 401 carries WWW-Authenticate: Bearer resource_metadata="https://api.0xinsider.com/.well-known/oauth-protected-resource" (RFC 6750 section 3, RFC 9728).

Scopes

read

Read markets, traders, large trades, positions, reports, search, the event stream and every MCP tool

Headers

X-Query-Validation
enum<string>

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Available options:
strict

Response

Missing or invalid API key

object
string
required
Allowed value: "error"
error
object
required
meta
object
required