predmarket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Live prediction-market data from Kalshi and Polymarket. Prices are YES probabilities between 0 and 1. Start with search_markets to find market ids, then use the other tools with the venue and id. Before treating a cross-venue price gap as an opportunity, check that both markets resolve on the same rules and date.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_marketsB | Find open markets by keywords, e.g. "fed rate cut december" or "bitcoin 150k". Returns market id, title, YES bid/ask/mid, volume and close time for each match. |
| get_marketA | Current quote and details for one market (Kalshi ticker or Polymarket slug). |
| get_orderbookB | YES-side order book: bids best-first, asks best-first, plus the spread. Kalshi NO bids are converted to YES asks (a NO bid at p equals a YES ask at 1 - p). |
| get_recent_tradesB | Most recent fills, newest first, each expressed as a YES price. |
| get_price_historyB | YES price history: hourly points up to 7 days, daily points beyond that (max 90 days). |
| compare_venuesB | Search both venues and pair markets that appear to ask the same question. price_gap = Polymarket mid minus Kalshi mid. Pairs must share the question's key words and agree on dates, place, stage, thresholds, direction and negation, and close at similar times, but they are still candidates: always confirm the resolution rules match before acting on a gap. |
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 6 tools
Each tool targets a distinct data need: discovery (search_markets), single-market quote (get_market), order book depth (get_orderbook), trade tape (get_recent_trades), time series (get_price_history), and cross-venue matching (compare_venues). The only superficial overlap is search_markets vs compare_venues, but the latter is explicitly scoped to pairing markets across two venues.
All six tools use a consistent snake_case verb_noun convention: search_markets, get_market, get_orderbook, get_recent_trades, get_price_history, compare_venues. There is no mixing of casing or verb styles.
Six tools is well-scoped for a read-only prediction-market data server. Each tool covers a distinct query surface and none appear redundant or gratuitous.
The surface covers discovery, quotes, order books, trades, history, and cross-venue comparison, which is strong for market data. A minor gap is that compare_venues warns users to confirm resolution rules, but no dedicated tool clearly exposes those rules; get_market may include details, but this is not explicit.