MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

PredictionScan

Derived prediction-market flow, price changes, trader research and news. 11 read-only tools.

Checks passed
15 / 22

0 failed · 7 not measured

Median response
538 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
11

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
103
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 567 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name predictionscan.

  • Pass
    Lists tools

    tools/list returned 11 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 538 ms over 2 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 564 ms over 2 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    2 of 2 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Pass
    Stable tool list

    No tool was removed and no required parameter was added in the last 30 days.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    28 of 28 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Pass
    Repo owner matches

    The GitHub repository owner matches the namespace login.

  • Pass
    Recently updated

    Updated 2026-11-01T19:40:20.555605Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using PredictionScan

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http predictionscan https://mcp.predictionscan.org/mcp

Capabilities

Tools 11

get_leaderboard

Use this when the user asks who the top Polymarket traders are by profit or by trading volume, or for a Polymarket leaderboard — for example "top Polymarket traders this month", "highest-profit traders this week", "highest-volume traders this week", or "top politics traders by realized profit". Returns up to 25 traders (default 10) from Polymarket.com's public leaderboard: rank, full wallet address, public display name, profit in USD for the period, and dollar trading volume, with a PredictionScan profile link for each trader. Periods: day (since 00:00 UTC), week (7 days), month (30 days) or all-time. Day/week/month profit counts open positions at current prices; all-time profit is realized only. Category boards (sports, politics, crypto, economics, finance, tech, culture, esports, weather, mentions) rank within that category; Polymarket does not publish per-category dollar volume, so it is null there. Read-only; past results do not predict future results. Do not use this to choose a market or trader for the user to put money in; it reports data only. Do not call this when the user asks which market to buy or how to make a profit.

Discovered
get_market_flow

Use this when the user asks who is buying or selling a Polymarket market, why its odds moved, or where the money is going, for example "who is buying Yes on the Fed October decision", "why did JD Vance's 2028 odds move today", "net buying on Bitcoin $150K this week", or "who holds the most of this market". Takes one market (a slug, a supported market or event link, a condition id, or plain words; for a multi-outcome event it uses the leading open outcome, or a ladder's most-traded open rung, and says so) and a window of 1 to 168 hours (default 24). Returns PredictionScan's flow breakdown from Polymarket.com's public trades: dollars bought and sold and the net per outcome, the trade count, up to 8 largest trades, and up to 5 top holders per outcome with their share counts. Dollar totals count each fill once (its taker side), so they run about half of the two-sided volume Polymarket.com headlines. In very busy markets small fills may be left out so the whole window fits; the text says so. Read-only: flow describes past trades, not where the price will go.

Discovered
get_market_movers

Use this when the user asks which Polymarket or prediction-market odds moved the most, what is rising or falling, or what changed today — for example "biggest movers on Polymarket", "which markets moved the most in the last 24 hours", "what odds are dropping in crypto", or "biggest swings in politics today". Returns up to 20 open Polymarket.com markets ranked by their 24-hour change in market-implied probability (points), with the outcome that moved, its probability and 24-hour volume; at most two per event. Optional filters: direction and category. Covers the 300 most-traded markets with at least $10K traded in 24 hours; markets at 1% or below or 99% or above are left out as effectively decided. Excludes individual sports and esports games (single matches and their side markets, live or upcoming) unless the category is sports or esports; futures such as a season or championship winner stay in. Mature topics are left out, and so are "Up or Down" and tweet-count markets without a category. Read-only crowd forecasts, not advice. Do not use this to choose a market or trader for the user to put money in. Do not call this when the user asks which market to buy or how to make a profit.

Discovered
get_market_news

Use this when the user asks for news, headlines or recent developments behind a prediction market or topic — for example "any news on the Fed October decision?", "what's in the news about Bitcoin ETFs?", "any headlines behind the move in the Fed October odds?", or "latest news on Gavin Newsom 2028". Pass a market (a slug from search_markets, or a supported market or event link) and/or topic words. Returns up to 10 headlines (default 5) from the last 14 days with the outlet, publish time and link, ranked by how many of the market's key names and terms they mention, newest first among equals. Headlines come from PredictionScan's news feed of major outlets (politics, economy, crypto, sports, entertainment): it is not a full web search, returns no article text, and may find nothing for niche markets.

Discovered
get_market_odds

Use this when the user wants the current odds or the details of one specific prediction market or event — for example "what are the odds for the Fed decision in October", "who leads the race for the 2028 Democratic nomination", "show me this market: polymarket.com/event/…", "what are the rules for this market", or "did the 2024 election market resolve, and to what". Accepts a market or event slug, a supported market or event link, a condition id, or the market's question in words. Returns each outcome's market-implied probability from Polymarket.com with its 24-hour change (up to 40 outcomes, mutually exclusive ones ranked, plus the total count), volume, liquidity, end date, status, the resolution rules and source, and the final result for resolved markets. Works for open, closed and resolved markets; when nothing matches it returns up to 3 of the closest open markets instead. Read-only: it cannot place trades, and probabilities are crowd forecasts, not advice. Do not call this when the user asks which market to buy or how to make a profit.

Discovered
get_price_history

Use this when the user asks how the odds of a prediction market have changed over time — for example "how have the Fed October odds moved this week", "chart the Bitcoin $150K odds over the last month", "when did Gavin Newsom's 2028 chances jump", or "show the price history of this market". Accepts a market or event slug, a supported market or event link, a condition id, or the question in words, plus an optional outcome name and time range (1d, 1w, 1m, 3m or all; default 1w). Returns the outcome's market-implied probability at the start and end of the range, the change in percentage points, the high and low, and a chart in the card. Prices come from Polymarket.com's order-book history; quiet markets can have gaps, which are left unfilled. For a closed or resolved market the range ends when trading closed. Read-only and informational, not advice.

Discovered
get_trader_positions

Use this when the user wants a Polymarket trader's open positions or holdings — for example "what positions does @exampletrader hold", "list all open positions for this 0x wallet", "what is this trader's biggest position", or "which of their positions are up the most". Accepts a full 0x wallet address, a polymarket.com profile URL, an @username or a username. Returns up to 50 open positions (default 20) sorted by current value or by unrealized profit, each with the market, outcome, shares held, average entry and current price in cents, current value and unrealized profit or loss in USD, plus the total number of open positions and the portfolio value. Positions worth under $1 and resolved positions awaiting redemption are left out of the list; the text notes the latter. Read-only public on-chain data.

Discovered
get_trader_profile

Use this when the user asks about one Polymarket trader or wallet — for example "how is this wallet doing on Polymarket" with a pasted 0x address, "show me @exampletrader's Polymarket stats", "who is this trader" with a polymarket.com profile link, or "what has this trader been trading lately". Accepts a full 0x wallet address, a polymarket.com profile URL, an @username or a username. Returns the public display name, all-time realized profit and dollar volume, current portfolio value, number of open positions, number of markets traded, up to five largest open positions and up to eight most recent trades of $1 or more. A username is matched exactly when possible; otherwise the closest public profile is used and the text says so. Read-only public on-chain data: it does not say who controls a wallet, and past results do not predict future results.

Discovered
get_trending_markets

Use this when the user asks what is trending, popular, hot or most traded on Polymarket or in prediction markets right now, or wants an overview of the biggest open markets in a category — for example "what's trending on Polymarket", "most popular prediction markets today", "top crypto markets right now", or "what are people trading on in politics". Returns up to 20 open Polymarket.com events with the most trading volume in the last 24 hours, each with up to four outcomes' market-implied probabilities (the leaders, or a price ladder's rungs nearest 50%), 24-hour change and volume. Optional category filter. Events that look settled (an outcome at 99% or more) and games' secondary prop sheets are left out. Excludes individual sports and esports games (single matches, live or upcoming) unless the category is sports or esports; futures such as a season or championship winner stay in. Mature topics, and without a category "Up or Down" and tweet-count markets, are also left out. Read-only crowd forecasts, not certainties or advice. Do not use this to choose a market or trader for the user to put money in. Do not call this when the user asks which market to buy or how to make a profit.

Discovered
get_whale_trades

Use this when the user asks about large or notable recent trades on Polymarket, for example "show me the biggest Polymarket trades today", "any large trades on the Fed decision?", "who made big trades on the 2028 election", or "trades over $50K this week". Scans Polymarket.com's public trade feed and returns up to 50 of the largest fills in the window (default 15), biggest first: time, buy or sell, outcome, dollar size, shares, price in cents, the market and its slug, and the trader's full wallet address and public display name. Optional filters: a minimum dollar size ($1K to $1M, default $10K), one market or event (a slug, a supported market or event link, a condition id, or plain words), and a window of 1 to 168 hours (default 24). Across all markets, fills at 99¢ or more or 1¢ or less (markets that are effectively decided) are left out, and so are individual sports and esports games and mature topics; name a market to see its trades. Each fill is counted once; dollars are shares times price. Read-only and informational: a large trade is not a forecast, and these tools cannot place trades.

Discovered
search_markets

Use this when the user asks about the odds, chances or likelihood of a real-world event, or what Polymarket or prediction markets say about something — for example "what are the odds the Fed cuts rates in October", "Polymarket odds for the 2028 election", "how likely is a US recession in 2026", "chances of Bitcoin hitting $150K this year", "what does the market say about a Ukraine ceasefire", "is there a prediction market on the 2028 Democratic nominee", "will the Fed cut rates in December", or "who will win the 2028 presidential election". Searches open Polymarket.com prediction markets and returns up to 10 closest matches (default 5), each with up to six outcomes' market-implied probabilities (outcomes the query names first, then the leaders, or a price ladder's rungs nearest 50%), 24-hour change and trading volume. For one market's full outcome list, rules and resolution status, use get_market_odds. Read-only: it cannot place trades, and the probabilities are crowd forecasts, not certainties or advice. Do not use this to choose a market or trader for the user to put money in; it reports data only. Do not call this when the user asks which market to buy or how to make a profit.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected567 ms11
Connected508 ms11