MCP server

Streamable HTTP MCP server (stateless, JSON responses): send one JSON-RPC 2.0 message per request with the same developer key as REST (Accept must list application/json and text/event-stream), and discover tools with tools/list. There is one read-only tool per major data endpoint, named after it (options_flow_stats for /v1/options/flow/stats); its arguments are the endpoint's query parameters and its result is the endpoint's response envelope as structured content. Each request, including every tools/call, counts as one request against the account rate limit; JSON-RPC batches are rejected. A failed call is a tool error holding the API error object.

Example request

curl -sS "https://api.ordermap.si/mcp" \
  -H "Authorization: Bearer $ORDERMAP_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

const res = await fetch("https://api.ordermap.si/mcp", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.ORDERMAP_API_KEY}`,
    "Content-Type": "application/json",
    Accept: "application/json, text/event-stream",
  },
  body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "tools/list" }),
});
console.log(await res.json());

Set ORDERMAP_API_KEY to your key. Replace the dates with a recent trading date.

Parameters

This endpoint takes no parameters.

Request body

Required. Content-Type: application/json

Tools

One read-only tool per major endpoint, named after it. The setup, the limits and the behaviour of failed calls are in the MCP guide. Each tool takes the query parameters of its endpoint.

Response

Authenticated responses carry the X-RateLimit-* headers (see rate limits); 429 and 503 add Retry-After.

200 response body