Prediction Market Intelligence
REMOTE · MCP.LACUNA.MARKETS
Polymarket in your AI: market rules, real fill costs, who is trading, top traders. Read-only.
Available components
Last scanned (1 hour ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.lacuna.markets/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lacuna.markets | CN=WE1,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 434bd2bfea09b3c50e85331484d205a0 |
| SANs: lacuna.markets, mcp.lacuna.markets, *.mcp.lacuna.markets | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.lacuna.markets. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| markets. | present | 58144, 64757 | 8, 8 | Verified |
| lacuna.markets. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lacuna.markets/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.lacuna.markets/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pm_book Order book and fill cost ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | For buy: dollars to spend. For sell: number of shares to sell. Omit to see the book only. |
| market | string | yes | 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. |
No output schema declared.
No examples provided.
pm_flow Who is trading ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
pm_leaderboard Top traders ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
pm_market Market brief ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | 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"). |
No output schema declared.
No examples provided.
pm_moves Biggest price moves ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
pm_portfolio Wallet positions ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | 0x wallet address, polymarket.com profile link (…/@name or …/profile/0x…), or Polymarket username. |
No output schema declared.
No examples provided.
pm_search Search markets ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of events to return (1–10, default 5). |
| query | string | yes | Keywords ("fed october", "bitcoin 150k", "house 2026") or a polymarket.com link. |
| status | string | – | open (default), resolved, or all. |
No output schema declared.
No examples provided.
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.
remote · mcp.lacuna.markets
claude mcp add --transport http markets-lacuna-prediction-market-intelligence 'https://mcp.lacuna.markets/mcp'
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.