# Prediction Market Intelligence (remote · mcp.lacuna.markets)

Polymarket in your AI: market rules, real fill costs, who is trading, top traders. Read-only.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.lacuna.markets`: 78/100 (this document), [markdown](https://verifymcp.io/servers/markets-lacuna-prediction-market-intelligence/mcp.md), [page](https://verifymcp.io/servers/markets-lacuna-prediction-market-intelligence/mcp)

## Channel facts

- Endpoint: `https://mcp.lacuna.markets/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1569 tokens (~196/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Prediction Market Intelligence MCP server?

Prediction Market Intelligence is a hosted endpoint at https://mcp.lacuna.markets/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http markets-lacuna-prediction-market-intelligence 'https://mcp.lacuna.markets/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "markets-lacuna-prediction-market-intelligence": {
      "url": "https://mcp.lacuna.markets/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "markets-lacuna-prediction-market-intelligence": {
      "type": "http",
      "url": "https://mcp.lacuna.markets/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.markets-lacuna-prediction-market-intelligence]
url = "https://mcp.lacuna.markets/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "markets-lacuna-prediction-market-intelligence": {
      "type": "remote",
      "url": "https://mcp.lacuna.markets/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add markets-lacuna-prediction-market-intelligence --url 'https://mcp.lacuna.markets/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  markets-lacuna-prediction-market-intelligence:
    url: "https://mcp.lacuna.markets/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "markets-lacuna-prediction-market-intelligence": {
      "Transport": "http",
      "Url": "https://mcp.lacuna.markets/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add markets-lacuna-prediction-market-intelligence -t streamable-http -u 'https://mcp.lacuna.markets/mcp'
```

### Other

```json
{
  "mcpServers": {
    "markets-lacuna-prediction-market-intelligence": {
      "type": "http",
      "url": "https://mcp.lacuna.markets/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `pm_search` (~169 tokens)

Search markets

Use this first when the user asks what Polymarket thinks about a topic, how likely something is, or names a market without a link. Searches every Polymarket market by keyword (Polymarket's own full-text search) or by a polymarket.com link and returns events with all their outcomes, current prices, 24h volume and end dates, plus the slug to pass to the other tools. Use status='resolved' for past markets and how they settled.

Input parameters:

- `limit` (integer): Number of events to return (1–10, default 5).
- `query` (string, required): Keywords ("fed october", "bitcoin 150k", "house 2026") or a polymarket.com link.
- `status` (string): open (default), resolved, or all.

### `pm_market` (~213 tokens)

Market brief

Use this when the user asks about one Polymarket market or event: its price, what exactly decides how it resolves, whether an outcome has been proposed or disputed, when it ends, its fees, or how it has moved. Returns prices, bid/ask and spread, change over 1h/24h/7d/30d with a 30-day range, volume and liquidity, taker fees, the resolution rules verbatim with their named source, and the live resolution status (not proposed / proposed and in its challenge window / disputed / resolved). For a multi-outcome event it lists every outcome and whether the prices add up to 100¢; add outcome to drill into one. Accepts a polymarket.com link or a slug from pm_search.

Input parameters:

- `market` (string, required): A polymarket.com link, or a market or event slug from pm_search.
- `outcome` (string): For a multi-outcome event: the outcome label to show in detail ("25 bps decrease").

### `pm_book` (~239 tokens)

Order book and fill cost

Use this when the user asks how liquid a Polymarket market is, how much a trade of a given size would really cost, how far it would move the price, or what the order book looks like. Returns the live book for one outcome: best levels, spread, dollar depth near the mid and which side is heavier. With amount it walks the book level by level for a market order (dollars to spend when buying, shares when selling) and returns shares filled, average and worst price, slippage against the mid, Polymarket's taker fee and the breakeven probability.

Input parameters:

- `amount` (number): For buy: dollars to spend. For sell: number of shares to sell. Omit to see the book only.
- `market` (string, required): A polymarket.com link, or a market or event slug from pm_search.
- `outcome` (string): Which outcome: "Yes"/"No", a team name, or for a multi-outcome event the outcome label ("25 bps decrease"). Default: the first outcome (usually Yes).
- `side` (string): buy (default) or sell.

### `pm_flow` (~244 tokens)

Who is trading

Use this when the user asks who is buying or selling a Polymarket market, why its price moved, where the money is going, who the biggest holders are, or (with no market) what the whales are doing across Polymarket. For a market or event: dollars traded and net direction per outcome, distinct wallets, the largest trades, the wallets that moved the most money, and for a single market the biggest current holders. With no market: the largest trades across all of Polymarket and the markets drawing that money. Traders appear by public username when they set one; pass a wallet to pm_portfolio for its full track record.

Input parameters:

- `hours` (integer): Look-back window in hours (1–168, default 24).
- `market` (string): A polymarket.com link, or a market or event slug from pm_search. Omit to see the largest trades across all of Polymarket.
- `min_usd` (number): Without a market: only trades of at least this many dollars (default $10,000).
- `outcome` (string): For a multi-outcome event: limit to one outcome by its label.

### `pm_moves` (~231 tokens)

Biggest price moves

Use this when the user asks what is moving, trending or changing on Polymarket, what moved overnight or this week, or for the biggest gainers and losers. Ranks the 300 most-traded open markets by price change over the last hour, day, week or month, with old and current price, the move in percentage points, 24h volume and the slug for follow-ups (pm_flow shows who moved it). Markets that are merely settling and live sports games are left out unless include_games is true.

Input parameters:

- `direction` (string): both (default), up only, or down only.
- `include_games` (boolean): Include individual sports games, whose prices move with the score (default false).
- `limit` (integer): Rows to return (1–20, default 10).
- `min_volume_24h_usd` (number): Skip markets that traded less than this in the last 24h (default $10,000).
- `window` (string): Look-back window: 1h, 24h (default), 7d or 30d.

### `pm_leaderboard` (~165 tokens)

Top traders

Use this when the user asks who the best or biggest Polymarket traders are, who made the most money today, this week, this month or all time, or who leads in a category (politics, sports, crypto, economics, finance, culture, tech, weather, mentions). Returns Polymarket's own leaderboard ranked by profit or by volume, with usernames and wallet addresses to pass to pm_portfolio.

Input parameters:

- `by` (string): Rank by profit and loss (pnl, default) or by dollar volume.
- `category` (string): overall (default) or one category.
- `limit` (integer): Rows to return (1–25, default 10).
- `period` (string): day, week (default), month or all.

### `pm_portfolio` (~158 tokens)

Wallet positions

Use this when the user asks what a Polymarket trader or wallet holds, how good a trader is, or wants to size up a wallet seen in pm_flow. Returns the track record (all-time and 30-day profit and loss, volume, leaderboard rank, markets traded), open positions with entry and current price, unrealized P&L, exposure grouped by event, settled winnings not yet redeemed, and recent trades. Accepts a 0x wallet address, a polymarket.com profile link or a Polymarket username. Public on-chain data only.

Input parameters:

- `wallet` (string, required): 0x wallet address, polymarket.com profile link (…/@name or …/profile/0x…), or Polymarket username.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/markets-lacuna-prediction-market-intelligence/mcp#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 67

## Common questions

### What is the Prediction Market Intelligence MCP server?

Prediction Market Intelligence is an MCP server listed in the public MCP registry as markets.lacuna/prediction-market-intelligence. Polymarket in your AI: market rules, real fill costs, who is trading, top traders. Read-only. This page covers its hosted endpoint (https://mcp.lacuna.markets/mcp).

### Is the Prediction Market Intelligence MCP server safe to use?

Prediction Market Intelligence scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Prediction Market Intelligence MCP server expose?

Prediction Market Intelligence exposes 7 tools: pm_search, pm_market, pm_book, pm_flow, pm_moves, and 2 more. Their descriptions and schemas cost roughly 1,419 tokens of context every time the server is loaded.

### Does the Prediction Market Intelligence MCP server require authentication?

No. We connected to Prediction Market Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Prediction Market Intelligence MCP server still maintained?

Prediction Market Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.lacuna.markets/mcp
- Website: https://lacuna.markets/
- Changelog RSS feed: https://verifymcp.io/servers/markets-lacuna-prediction-market-intelligence/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/markets-lacuna-prediction-market-intelligence/mcp.json
- HTML version of this page: https://verifymcp.io/servers/markets-lacuna-prediction-market-intelligence/mcp