Kalshi MCP server

kalshi

Market data from Kalshi, the CFTC-regulated US prediction-market exchange. Public reads need no credential; nothing in this pack ever touches an account.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Upstream: https://api.elections.kalshi.com/trade-api/v2 (docs: , which serves every endpoint page as .md).

What is here

Bold rows landed 2026-09-16 (fleet #2040). The bucket assignment for all eight probed endpoint families, with the literal responses, is in docs/pack-build-queue.md.

Traps already paid for

Kalshi filters Cloudflare egress on its listing endpoints. Several endpoints return empty to a Workers IP. The gateway injects proxyUrl/proxyToken and kalshiGet() routes every upstream fetch through the relay when they are present. Anything new must go through kalshiGet, never a bare fetch.

Auth-gated vs broken is legible on this API, so check before concluding. An endpoint that needs a credential answers 401 {"error":{"code":"tokenauthenticationfailure"}}. A 400 bad_request is the handler refusing, not a missing key.

/markets/orderbooks takes tickers repeated; /markets/candlesticks takes markettickers comma-separated.** Two batch endpoints on the same API, two different array conventions. Getting it wrong is a 400, not a silent subset.

The batch candlestick response labels each group marketticker, not ticker.** Pair by that label. Pairing by request order would attribute one market's entire price history to another and still return 200.

Kalshi caps batch candlesticks at 10,000 candles across ALL requested markets and gives no cursor there. kalshicandlesticks reports truncatedbyupstream. For one ticker over a long window — or a market old enough to be archived — use kalshiprice_history, which pages and falls back to the archive; the batch endpoint does neither.

/livedata/events/{ticker} is 404 for most events, and that is normal. It exists for crypto price events and some economic-series events. found:false is the honest answer, not an error. A live BTC event's payload is ~473 KB, which is why series are trimmed to maxpoints with series_trimmed reporting the untrimmed length.

Weather is city-keyed, not event-keyed. KXHIGHNY-26SEP16 404s on the event live-data endpoint. The observations live at /live_data/weather/{city} and exist whether or not a market is open.

Shortened. The full README is on GitHub.