Servidor MCP de pdata

• Nombre en el registroworld.pdata/mcpverificado en el registro MCP

El nombre en el registro está bajo pdata.world. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-21
• Herramientas14
• El servidor se llamapdata — prediction markets
• Versión del servidor2.4.3
• Versión del protocolo2025-06-18

El 2026-10-21 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 267 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 6 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 6 hasta ahora
• Respondiómidiendo6 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta598 ms
• Espacio en el contexto del agente≈ 11.397 tokenslas definiciones de todas sus herramientas (14), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados0 de 14 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• 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…

• 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…

• 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.

• 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…

• 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…

• 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`, among open markets that moved more than 2 points on over 1,000 units of 24h…

• 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. Takes the /markets filters, e.g. `source=` and `categories=` (CSV); price-derivative markets are…

• 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` /…

• 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…

• 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…

• 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 after each Polymarket ingest cycle, typically…

• 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…

• 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).