Skip to main content
POST
/
api
/
v1
/
mcp
Remote MCP endpoint (JSON-RPC)
curl --request POST \
  --url https://api.0xinsider.com/api/v1/mcp \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "<string>",
  "method": "initialize",
  "id": "<string>",
  "params": {}
}
'
{
  "jsonrpc": "<string>",
  "id": "<string>",
  "result": {},
  "error": {
    "code": 123,
    "message": "<string>"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.0xinsider.com/llms.txt

Use this file to discover all available pages before exploring further.

Use Authorization: Bearer <token> for remote MCP clients that support custom headers. The ?token= query parameter remains available only as legacy compatibility for URL-only clients; prefer headers because URL secrets can be stored in shell history, browser history, proxies, and logs.

Authorizations

​
Authorization
string
header
required

API key: Authorization: Bearer oxi_sk_live_...

Headers

​
Mcp-Session-Id
string

Session ID minted by the server on initialize; echoed on every subsequent request.

Query Parameters

​
token
string

Deprecated compatibility API-key query parameter for remote MCP clients that cannot send Authorization headers. Prefer Authorization: Bearer or the stdio package because URL secrets are easier to leak through logs and history.

Body

application/json
​
jsonrpc
string
required
Allowed value: "2.0"
​
method
enum<string>
required
Available options:
initialize,
notifications/initialized,
ping,
tools/list,
tools/call
​
id
​
params
object

Response

JSON-RPC response

​
jsonrpc
string
required
Allowed value: "2.0"
​
id
required
​
result
object
​
error
object