Kalshi Screener MCP
Related Servers
Alternatives to Kalshi Screener MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceLets AI agents query real Kalshi market data by searching markets, retrieving market details, and reading order books, using only public GET requests with no Kalshi account or API keys.-
- AlicenseNot gradedqualityBmaintenanceProvides access to US-regulated prediction-market data from Kalshi, enabling queries on market events without authentication.96 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides access to Kalshi prediction market data with 23 tools for querying events, markets, trades, forecasts, candlesticks, and live data from the CFTC-regulated exchange for trading on real-world events.7-
- AlicenseAqualityCmaintenanceEnables Claude Desktop, Cursor, and other AI agents to query prediction markets, inspect Level 2 orderbooks, calculate regulatory fees and arbitrage breakevens, estimate implied probabilities, and scan cross-venue spreads.564 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search Kalshi, Polymarket and Limitless prediction markets by keyword, venue, category or status, inspect series and market details, and review recorded YES bid/ask price history over a market's life. It also reports recording coverage and lists datasets, letting users browse or download daily order book Parquet files with an API key.1040 PyPI1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to aggregate live prediction-market odds across Polymarket, Kalshi, and Manifold and scan for cross-venue probability spreads and arbitrage edges, with a zero-config remote or stdio setup and a free daily call tier.2314 npmMIT
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes: screen CRUD, market search/detail, event detail, evidence, watchlist, and alerts. There is minor overlap because list_saved_screens also mentions presets and the watchlist, while get_watchlist and list_alerts cover related extension data, but descriptions make the boundaries mostly clear.
All tool names use consistent snake_case with a predictable verb_noun pattern such as get_market, search_markets, save_screen, and delete_screen. The verbs are standard and readable throughout.
Ten tools is well-scoped for a market screener and research server. Each tool appears to earn its place by covering a distinct part of the screening, saved-screen, market-detail, or monitoring workflow.
The surface covers the core lifecycle well: save/list/run/delete screens, search markets, inspect markets/events, retrieve evidence, and read watchlist/alerts. Minor gaps exist, such as no update/rename operation for saved screens and no alert management beyond listing recent matches.