Kalshi Screener MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KALSHI_SCREENER_EXTENSION_ID | No | Sets the extension ID used in links before the extension has shared data. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_marketsC | Screen open Kalshi markets by price, time to close, listing age, volume, spread, daily change and event structure. |
| get_marketA | Prices, top of the order book, rules, settlement sources and the other markets in the same event for one market ticker. Includes research_prompt, a brief for researching the market with web search or a browser tool. |
| get_market_evidenceA | How past events in the same Kalshi series settled: how often markets priced near this market's current price at the same time before close settled YES, how often the favorite won, and the most recent events. Every rate comes with its sample size and a 95% range. Use it for questions like "will this go up?" or "is this likely?", and explain the numbers instead of predicting. |
| get_eventB | All open markets in one Kalshi event ranked by YES price, with YES bid and ask totals. |
| save_screenA | Save search filters under a name so they can be run again with run_saved_screen. |
| delete_screenA | Delete a screen saved through this server. Screens saved in the Chrome extension are not affected. |
| list_saved_screensB | Screens saved through this server plus condition presets and the watchlist shared by the Chrome extension. |
| run_saved_screenB | Run a screen saved through this server or a condition preset shared by the Chrome extension, by name or id. |
| get_watchlistB | Current prices for the markets saved in the Chrome extension watchlist. |
| list_alertsC | Recent condition matches recorded by the Chrome extension's background monitor. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.