INDIVIDUAL MCP TOOL

map_timeline

Use when you need the hourly total-heat time series that drives the /map playback scrubber.

pdata.worldnone authenticationAvailability not checked

LIVE ENDPOINT

https://api.pdata.world/mcp

No auth detected

Connect to this endpoint to inspect the live schema for map_timeline and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pdata-prediction-markets]
url = "https://api.pdata.world/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pdata-prediction-markets": {
      "type": "http",
      "url": "https://api.pdata.world/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pdata-prediction-markets
Remote MCP URL: https://api.pdata.world/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pdata-prediction-markets": {
      "url": "https://api.pdata.world/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pdata-prediction-markets": {
      "type": "http",
      "url": "https://api.pdata.world/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pdata-prediction-markets",
  "transport": "streamable-http",
  "url": "https://api.pdata.world/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

list_events — Use when an agent wants to browse, filter, or search prediction-market events across all 8 platforms.
get_event — Use when an agent needs the full detail of a single prediction-market event by its composite key (source + event_id).
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.
list_markets — Use when the user wants to browse, filter, or sort individual markets (not events).
get_market — Use when an agent needs the full detail of a single market by its composite key (source + market_id).
top_movers — Use when the user wants to see markets with the largest 24h probability swings.
closing_soon — Use when the user wants to see markets that will resolve within the next 36 hours.
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.