pdata Prediction Markets is answering right now. Last checked 12 min ago. It exposes 14 tools.
Live prediction-market odds, volume and movers across 8 platforms. Read-only, no auth.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
11 hours of history
11 hours agonow
100.0%
Uptime 24h
37 of 37 checks
14
Tools
read from the server
534 ms
Response time
average over 24h
open, no key
Access
streamable-http
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.
run in your terminal
claude mcp add mcp --transport http https://api.pdata.world/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"url": "https://api.pdata.world/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.pdata.world/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://api.pdata.world/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://api.pdata.world/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
event
get_event
Use when an agent needs the full detail of a single prediction-market event by its composite key (source + event_id). Returns the event with all of its child markets, latest probabilities, and metadata. The canonical URL `https://pdata.world/events/{source}/{event_id}` is stable for the lifetime of the underlying market. Events that closed more than 10 days ago are removed from the live tables; the same URL then returns a `kind: "tombstone"` object holding the title, close date and final outcome of each top market instead of the live `kind: "live"` object. Check `kind` before reading any other field.
get_event_similar
Use when an agent needs events similar to a given event — cross-platform equivalents and topically-related markets, precomputed nightly from title embeddings. Best-first; empty list (never an error) when no similarities are known yet.
map
map_heat
Use when you need a geographic snapshot of where prediction-market attention is concentrated. Returns per-country heat (capped news score, summed) for the current moment (`at=now`) or a past hour (`at=<ISO8601>`).
map_timeline
Use when you need the hourly total-heat time series that drives the /map playback scrubber. History accretes from launch (no backfill).
news
list_news_movers
Use when the user wants to see the news-feed view: markets that exhibited a probability spike in the chosen lookback window, scored by `|Δprob_pp| × log10(1+USD-equivalent volume)`. Refreshed every 5 min. The `window=` param selects the lookback: 24 (default, ≥15pp), 12 (≥12pp), or 2 (≥2h, ≥10pp); `prob_change` is measured over that window. Includes a `prob_history` array (24h bucketed trajectory) per row regardless of window. Filterable by `source=` and `categories=` (CSV). Soft flags (`is_entertainment`/`is_microprediction`/`is_crypto`/`is_sports`/`is_weather`) default OFF; opt in with `include_*=true`.
news_movers_by_category
Use when the user wants the news feed bucketed by category. Returns the same data shape as `list_news_movers` but pre-grouped into the canonical 14-category vocabulary, with cluster grouping inside each bucket. Useful for 'what's moving in politics?' style queries.
closing
closing_soon
Use when the user wants to see markets that will resolve within the next 36 hours. Returns markets sorted by close timestamp ascending. Filterable by `source=` and `categories=` (CSV). Excludes Limitless and price-derivative markets.
countries
list_countries
Use when an agent needs the list of country tags that markets have been tagged with. Returns the canonical country vocabulary with per-country market counts. Accepts the same filter params as `list_markets` (source, category, status, volume/probability ranges, search, …): the counts then reflect that filtered population, so this doubles as a facet endpoint. The country dimension itself is ignored when computing counts, so passing `country=` does not collapse the menu. Useful as the menu source for the `country=` filter on `list_events` / `list_markets` / `top_movers`.
events
list_events
Use when an agent wants to browse, filter, or search prediction-market events across all 8 platforms. Returns paginated events with their child markets, prices, and platform metadata. Filterable by source (polymarket/kalshi/manifold/myriad/limitless/predict/opinion/gemini), category, country, status (open/closed), and full-text search via `search`. Sortable by `volume_24hr`, `normalized_vol_24hr`, `liquidity`, `end_date`, or `closed_time` (prefix `-` for descending). Cap `page_size` ≤ 50 to keep responses small enough for LLM context windows.
market
get_market
Use when an agent needs the full detail of a single market by its composite key (source + market_id). Returns the market with its parent event reference, current probability, volume, 24h delta, and historical chart points. Includes a `_meta.cite_as` field that the agent can drop directly into its reply.
markets
list_markets
Use when the user wants to browse, filter, or sort individual markets (not events). Returns paginated markets with their probability, volume, source, parent event ID, and 24h delta. Filterable by source, country, category, status, and full-text `search`. Sortable by `volume_24hr` or `probability`. Cap `page_size` ≤ 50 for chat-friendly responses.
suggest
search_suggest
Use when an agent has a name or phrase and needs the `(source, id)` of the matching event or market before calling another tool. Resolves free text against events AND markets in one call, best-first, and reports `total_events` / `total_markets` so the agent can tell a precise hit from an ambiguous one. Every row carries `event_path`, the internal link to use for follow-up lookups. Prefer this over running `list_events?search=` and `list_markets?search=` separately when the goal is identification rather than a filtered listing. Note: `headline` carries literal `<b>` highlight markup — quote `title` instead, or strip the tags.
summary
get_summary
Use when an agent needs platform-level context before drilling into individual markets: one row per platform (Polymarket, Kalshi, Manifold, Myriad, Limitless, Predict, Opinion, Gemini) carrying 24h notional volume, active event and market counts, and that platform's category mix. Takes no parameters and returns the whole picture in one small response, which makes it the cheapest way to answer 'how big is X relative to Y' or 'which platform covers this topic'. Volumes are in each platform's native units — Manifold reports play-money mana, not USD — so do not sum across platforms without saying so.
top
top_movers
Use when the user wants to see markets with the largest 24h probability swings. Returns the top N movers (default 5, max 20) ranked by absolute `prob_24h_change`. Filterable by source. Excludes Limitless and price-derivative markets by curation. Useful for 'what changed today?' style queries.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.pdata.world/mcp | streamable-http | answering | 652 ms | 12 min ago |
Alternatives to pdata Prediction Markets
same job, measured the same wayPolymarket MCP
by 0xchron
Read-only Polymarket prediction market data for AI agents.
Kalshi
by pipeworx-io
Kalshi MCP — US-regulated prediction-market data (no auth on public reads).
Reporting Ninja
by reportingninja
Read-only access to your Reporting Ninja marketing and analytics data across 20+ ad platforms.
Polymarket News MCP
by mobymedia
Match news headlines to the Polymarket prediction markets they move - live odds and deep links
Spoiler
by zerozaky
Sealed prediction-market verdicts, graded in public across Polymarket and Kalshi. No auth required.
Prediction Markets API
by br0ski777
Prediction market odds from Polymarket. Active markets, probabilities, volume. x402.
M
Bellwether
by bellwether
Live Kalshi + Polymarket prediction-market data and cross-venue arbitrage spreads, one schema.
Odds API
by frontofgoal
Live soccer prediction-market odds and order-book depth from Polymarket.
pdata Prediction Markets — questions
Answers built from our own checks of this server.
What can pdata Prediction Markets do?
It exposes 14 tools, read directly from the server on our last check. Among them: closing_soon, get_event, get_event_similar, get_market, get_summary, list_countries and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is pdata Prediction Markets mostly used for?
Its tools cluster around event, news and map. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is pdata Prediction Markets working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 37 of 37 checks got a reply (100.0%), average response time 534 ms. The bar chart above shows every period we have measured.
Is pdata Prediction Markets still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect pdata Prediction Markets?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does pdata Prediction Markets need an API key?
No. pdata Prediction Markets completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is pdata Prediction Markets?
It answers our handshake in 534 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.