io.github.yakub268/kalshi
io.github.yakub268/kalshi
Is the io.github.yakub268/kalshi MCP server down? Yes. It has given no valid answer since 2026-10-17: install failed.
Search, analyze, and trade Kalshi prediction markets through Claude Desktop
install failed down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31
error: Failed to install entrypoints for `kalshi-mcp`
- Run it
- uvx kalshi-mcp@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/yakub268/kalshi-mcp
- Registry
- active, updated 2026-02-21 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Verbatim Transcribe io.github.xyzxinlu-max/verbatim-transcribe-mcp · alive
- db-compare io.github.yadu-tv/db-compare · crashed on start
- ReClip io.github.yagyaanshK/reclip · alive
- FrankenSurf io.github.yail259/frankensurf · crashed on start
- io.github.yakuphanycl/instinct · not found
- io.github.yamantaka520/agent-memory-os · needs args
- TopicForge io.github.yaniswav/topicforge · alive
- io.github.yantrikos/yantrikdb-mcp · alive
Servers that mention kalshi.
- app.oddsrail/polymarket-kalshi-trading · needs auth
- Crosswire — Polymarket & Kalshi Arbitrage com.crosswire-api/crosswire-polymarket-kalshi-arbitrage · alive
- DepthFeed com.depthfeed/depthfeed · alive
- EloEdge: Kalshi model probabilities com.eloedge/kalshi-prediction-markets · needs auth
- Predict — Prediction Market Data for AI Agents com.gocreativeai.predict/predict · server error
- Kalshi MCP com.kalshi-mcp/kalshi · needs auth
- Macro & Commodities Desk com.predictionmarketspicks/commodities · alive
- Prediction Markets Quant com.predictionmarketspicks/quant · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.