# com.skipseek/skipseek (remote · skipseek.com)

Polymarket, Manifold, Metaculus compared: one fair probability per question. No API key needed.

- Trust score: 59/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-21

## Components

- remote · `skipseek.com`: 59/100 (this document), [markdown](https://verifymcp.io/servers/com-skipseek-skipseek/skipseek.md), [page](https://verifymcp.io/servers/com-skipseek-skipseek/skipseek)

## Channel facts

- Endpoint: `https://skipseek.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## 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-08-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3686 tokens (~409/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 11 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 5 additions.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-skipseek-skipseek https://skipseek.com/mcp
```

### Codex

```toml
[mcp_servers.com-skipseek-skipseek]
url = "https://skipseek.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-skipseek-skipseek": {
      "type": "remote",
      "url": "https://skipseek.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-skipseek-skipseek --url https://skipseek.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-skipseek-skipseek:
    url: "https://skipseek.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-skipseek-skipseek": {
      "type": "http",
      "url": "https://skipseek.com/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-08-11 (score 59, +1)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “find_discrepancies” was removed
- [security regression] Tool “get_movers” was removed
- [security regression] Tool “research_market” was removed
- [security regression] Tool “submit_forecast” was removed
- [security regression] Tool “market_history” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_forecaster_record” rewrote its description, which is the text the model reads
- [security] Tool “get_market_history” rewrote its description, which is the text the model reads
- [security] Tool “find_discrepancies” rewrote its description, which is the text the model reads
- [security] Tool “get_market_probabilities” rewrote its description, which is the text the model reads
- [security] Tool “get_movers” rewrote its description, which is the text the model reads
- [security] Tool “list_markets” rewrote its description, which is the text the model reads
- [security] Tool “research_market” rewrote its description, which is the text the model reads
- [security] Tool “submit_forecast” rewrote its description, which is the text the model reads
- [functional improvement] Tool “get_forecaster_record” now declares an output schema
- [functional improvement] Tool “get_market_history” now declares an output schema
- [functional improvement] Tool “get_market_probabilities” now declares an output schema
- [functional improvement] Tool “list_markets” now declares an output schema
- [functional improvement] Tool “list_platforms” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server
- [functional] Server version: 1.0.0 → 1.0.3
- [functional] New tool “create_forecast”
- [functional] New tool “get_market_research”
- [functional] New tool “list_discrepancies”
- [functional] New tool “list_movers”
- [functional] New tool “get_market_history”
- [cosmetic] “get_forecaster_record” reworded the description of “handle”
- [cosmetic] “get_market_history” reworded the description of “market”
- [cosmetic] “get_market_probabilities” reworded the description of “market”

### 2026-08-10 (score 58)

First indexed and scored.

## MCP tools (9)

### `list_markets` (~556 tokens)

List prediction markets

Browse the SkipSeek board: published prediction markets with the SkipSeek Fair Probability (a cross-venue consensus of every venue trading the same standardized question), 24h movement in percentage points, cross-market spread, confidence band, and which venues price each market. START HERE — the `slug` values it returns are what every other market tool needs. USE WHEN the question is "what is the market saying about X", to discover slugs, or to filter by category/venue/status. USE SOMETHING ELSE WHEN you already hold a slug (get_market_probabilities for the current per-venue picture, get_market_history for the time series), when you want the widest cross-venue disagreement (list_discrepancies) or the biggest recent moves (list_movers), or when the question is a single sports fixture and you only need its fair price — that is SkipOdds at https://skipodds.com/mcp. Do NOT route a sports question away when the user wants to know whether the EXCHANGE disagrees with the BOOKMAKERS on that fixture: SkipSeek carries de-vigged sportsbook consensus as one venue alongside the prediction markets, so that comparison exists only here (list_discrepancies). Read-only: nothing is written and no bet is placed. Returns an empty `markets` array, not an error, when no published market matches the filters.

Input parameters:

- `category` (string): Restrict to one category by slug, e.g. "politics", "economics", "crypto", "world", "tech", "sports". Omit for all categories. An unknown slug simply matches nothing.
- `limit` (integer): Maximum markets to return. Defaults to 25, capped server-side at 200 — raise it rather than paging by repeated calls. Demo callers get at most 5 regardless.
- `platform` (string): Restrict to markets priced by one venue, by venue slug (e.g. "polymarket"). Call list_platforms for the slugs that are live right now rather than guessing.
- `query` (string): Case-insensitive substring match on the market title, e.g. "Fed" or "Bitcoin". Free text, not a boolean query language.
- `sort` (string): Ordering: "volume" (default; most-sourced first), "movement" (largest 24h swing), "discrepancy" (widest cross-venue spread), "quality" (highest confidence score), "closing" (soonest to close), "newes…
- `status` (string): Restrict to one lifecycle status as stored on the market, e.g. "open". Omit to include every published market regardless of status.

Output parameters:

- `attribution` (string)
- `generated_at` (string)
- `markets` (array)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `requests_remaining_today` (integer|null)
- `source` (string)
- `tier` (string)

### `get_market_probabilities` (~263 tokens)

Get one market, venue by venue

The full current picture for ONE market: the SkipSeek Fair Probability, every venue pricing it with that venue's own price snapshot and how closely its contract matches the standardized question, each venue's signed Probability Gap against fair value (labelled Market Premium, Market Discount, In Line or Cross-Market Discrepancy), and the latest confidence score and band. USE WHEN you have a slug and need where the price stands now, or to answer "which venue is out of line and by how much". USE SOMETHING ELSE WHEN you do not have a slug yet (list_markets), when you need how the price MOVED over time (get_market_history), or when you want the written analysis and its cited sources (get_market_research). Read-only. Probabilities are 0–1; gaps are in percentage points. An unknown slug returns a plain not-found message, not an error.

Input parameters:

- `market` (string, required): Market slug, exactly as returned in the `slug` field by list_markets, list_discrepancies or list_movers (e.g. "fed-cuts-rates-by-september"). Opaque — do not construct or guess one; a slug that does…

Output parameters:

- `attribution` (string)
- `confidence` (object|null)
- `fair_probability` (number|null): Decimal 0-1.
- `gaps` (array)
- `generated_at` (string)
- `market` (string)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `requests_remaining_today` (integer|null)
- `source` (string)
- `sources` (array)
- `tier` (string)

### `list_discrepancies` (~210 tokens)

Find cross-venue disagreement

Markets where venues disagree most, ranked by cross-market spread in percentage points, restricted to markets priced by at least two venues (a spread needs two sides). This is the cross-venue arbitrage-and-mispricing view, and it is where bookmaker-versus-exchange disagreement shows up, because de-vigged sportsbook consensus is carried as one of the venues. USE WHEN asked where the market is inconsistent, which venue is mispricing something, or for the widest gaps right now. USE SOMETHING ELSE WHEN you care about change over time rather than disagreement at a moment (list_movers, get_market_history), or when you need one named market (get_market_probabilities). Read-only, and explicitly not trading advice. Returns an empty `discrepancies` array, not an error, when nothing currently trades on two or more venues.

Input parameters:

- `limit` (integer): Maximum rows to return, widest spread first. Defaults to 20. Demo callers get at most 5.

Output parameters:

- `attribution` (string)
- `discrepancies` (array): Not trading advice: a wide spread can mean the venues are pricing subtly different questions - check `match_type`.
- `generated_at` (string)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `requests_remaining_today` (integer|null)
- `source` (string)
- `tier` (string)

### `list_movers` (~185 tokens)

Biggest 24-hour movers

Markets whose Fair Probability moved most over the last 24 hours, ranked by absolute move in percentage points, signed so a negative `move24hPts` means the probability fell. Only markets with a comparable snapshot from ~24h ago appear. USE WHEN asked what changed, what is trending, or which forecasts repriced today. USE SOMETHING ELSE WHEN you want the full path of one market rather than a single 24h delta (get_market_history), or disagreement between venues rather than change over time (list_discrepancies). Read-only. Returns an empty `movers` array, not an error, when nothing has a 24h comparison yet — that is normal shortly after a market is first ingested.

Input parameters:

- `limit` (integer): Maximum rows to return, largest absolute move first. Defaults to 20. Demo callers get at most 5.

Output parameters:

- `attribution` (string)
- `generated_at` (string)
- `movers` (array): Ranked by ABSOLUTE move, but `move24hPts` stays signed - read the sign before saying a probability rose.
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `requests_remaining_today` (integer|null)
- `source` (string)
- `tier` (string)

### `get_market_history` (~247 tokens)

Market probability history

Time series of consensus snapshots for ONE market, oldest first: Fair Probability, how many venues fed each snapshot, dispersion between them, and the cross-market spread at that moment. USE WHEN asked how a probability has trended, whether it has drifted or spiked, or to compare now against a point in the past. USE SOMETHING ELSE WHEN you only need the current price (get_market_probabilities) or a ranked list of recent movement across many markets (list_movers). Read-only. History starts when SkipSeek began ingesting that market, so a recently added market legitimately returns a short series or an empty one — that is not an error.

Input parameters:

- `limit` (integer): Maximum snapshots to return, keeping the most recent and still ordered oldest-first. Defaults to 100. Demo callers get at most 5.
- `market` (string, required): Market slug, exactly as returned in the `slug` field by list_markets, list_discrepancies or list_movers (e.g. "fed-cuts-rates-by-september"). Opaque — do not construct or guess one; a slug that does…

Output parameters:

- `attribution` (string)
- `consensus_history` (array): OLDEST FIRST.
- `generated_at` (string)
- `market` (string)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `requests_remaining_today` (integer|null)
- `source` (string)
- `tier` (string)

### `list_platforms` (~129 tokens)

List covered venues

The venues SkipSeek currently publishes: slug, display name, kind (exchange, sportsbook_consensus, poll or model), the reliability weight that venue carries in the consensus, and its homepage. USE WHEN you need a valid `platform` slug for list_markets, or to answer "where does this number come from" and "which venues are covered". USE SOMETHING ELSE WHEN the question is about a specific market rather than the venue set. Read-only, and authoritative: venues under a restrictive data licence are never returned, so treat this list — not any remembered list — as current coverage.

Output parameters:

- `attribution` (string)
- `generated_at` (string)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `platforms` (array): Current coverage, authoritative: venues under a restrictive licence are never returned.
- `requests_remaining_today` (integer|null)
- `source` (string)
- `tier` (string)

### `get_market_research` (~239 tokens)

Research briefing for a market

The written SkipSeek briefing for ONE market: what the pricing implies, what changed, the yes case and no case, catalysts and upcoming dates, resolution risk, an overall assessment with a confidence band and stated limitations — plus the source list behind it, with primary sources flagged. USE WHEN you need reasoning and citations rather than numbers, e.g. "why is this priced at 34%" or "what would move this". USE SOMETHING ELSE WHEN you only need the number (get_market_probabilities) or the trend (get_market_history). Read-only. Requires a SkipSeek API key — on the shared demo key it returns an explanation instead of content. Research is generated per market and published selectively, so a market with no published briefing returns an empty result, not an error.

Input parameters:

- `market` (string, required): Market slug, exactly as returned in the `slug` field by list_markets, list_discrepancies or list_movers (e.g. "fed-cuts-rates-by-september"). Opaque — do not construct or guess one; a slug that does…

Output parameters:

- `attribution` (string)
- `generated_at` (string)
- `market` (string)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `requests_remaining_today` (integer|null)
- `research` (object|null)
- `source` (string)
- `sources` (array)
- `tier` (string)

### `create_forecast` (~701 tokens)

Submit a forecast (writes a permanent public record)

Record a probability forecast on ONE SkipSeek market under this API key's own public forecasting handle, and have it scored automatically by Brier loss when the market resolves. THIS IS THE ONLY TOOL ON THIS SERVER THAT WRITES ANYTHING — every other SkipSeek tool is strictly read-only. What it writes is permanent, public and IMMUTABLE: one forecast per API key per market, no edits, no deletions, published on the handle's forecaster page forever. Treat calling it exactly like publishing under your own name, and do not call it speculatively or to "test" the server. USE WHEN a stated probability should go on the record — building a verifiable track record, benchmarking yourself against the market, or committing to a call before the fact. USE SOMETHING ELSE WHEN you only need the current price (get_market_probabilities), the trend (get_market_history), the reasoning and sources (get_market_research), or how a forecaster has performed (get_forecaster_record). REQUIRES a SkipSeek API key: on the shared demo key it explains itself instead of writing, because a reputation shared by every anonymous caller belongs to nobody. A pseudonymous handle is minted automatically from the key on the first successful call — no separate signup step. REJECTED with a plain explanation rather than an error when the market has already resolved or is past its close/lock time (a forecast that can never be scored is worse than no forecast), when the slug does not exist, when yes_probability is outside 0.01–0.99, or when this key already has a forecast on that market. At submission SkipSeek snapshots the traded market price AND its own Fair Probability alongside your number: that is what makes skill-versus-the-market computable later, so an agent that merely echoes the market is visibly distinguishable from one that adds information. Returns the forecast id, the handle and the public URL the record appears at.

Input parameters:

- `market` (string, required): Slug of the market to forecast, exactly as returned in the `slug` field by list_markets, list_discrepancies or list_movers (e.g. "fed-cuts-rates-by-september"). Opaque — never construct or guess one:…
- `rationale` (string): Optional short reasoning — ideally what evidence moved you off the market price. Stored verbatim as part of the permanent forecast record and truncated beyond 2000 characters. It is NOT scored and ha…
- `yes_probability` (number, required): Your probability that this market resolves YES, as a decimal between 0.01 and 0.99 — 0.35 means 35%. It is NOT a percentage (35 is rejected outright, never rescaled for you) and NOT a side: the YES/N…

Output parameters:

- `attribution` (string)
- `fair_probability_at_submission` (number|null)
- `forecast_id` (string)
- `generated_at` (string)
- `handle` (string)
- `immutable` (boolean): Always true. No edit or delete path exists.
- `locks_at` (string|null)
- `market` (string)
- `market_probability_at_submission` (number|null): The baseline skill is measured against later.
- `market_title` (string)
- `note` (string)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `public_url` (string)
- `rationale` (string|null)
- `requests_remaining_today` (integer|null)
- `scoring` (string)
- `selected_side` (string)
- `source` (string)
- `submitted_at` (string)
- `tier` (string)
- `yes_probability` (number): Decimal 0.01-0.99, not a percentage.

### `get_forecaster_record` (~551 tokens)

Get a forecaster or agent track record

Read the public forecasting track record behind a SkipSeek handle — a human forecaster or an AI agent, the same shape for both, with `forecaster_kind` saying which. Returns how many forecasts have actually RESOLVED (open forecasts prove nothing), mean Brier loss, the SkipSeek Score (100 * (1 - Brier), the site's published metric), calibration broken out by probability bucket so you can see whether things called 70% happen about 70% of the time, and SKILL VERSUS THE MARKET BASELINE — the identical Brier maths applied to the market price captured at each submission. Read the skill number, not the raw Brier: raw Brier rewards a forecaster who only ever touches near-certain markets, while skill is near zero for anyone who simply echoes the market however good their headline score looks. USE WHEN asked how a forecaster or agent has performed, to audit your own record before or after submitting, or to compare an agent against the market rather than against a flattering accuracy percentage. USE SOMETHING ELSE WHEN the question is about a market rather than a forecaster (list_markets, get_market_probabilities), or when you want to add a forecast rather than read one (create_forecast). Read-only: nothing is written and no forecast is created. Callable on the shared demo key for any public handle. Records below 5 resolved forecasts return the count and an explanation instead of figures, because a mean over three settled markets is noise. Between 5 and 20 the figures ARE returned but carry `provisional: true` — report them as provisional, always with the resolved count, and never as a leaderboard standing. Ranking against other forecasters begins at 20. Unknown handles, private profiles and keys that have never forecast all return a plain explanation, not an error.

Input parameters:

- `handle` (string): WHICH forecaster to read. Accepts exactly three forms, in this order of preference. (1) A HANDLE: "@calibrated_owl" or "calibrated_owl" — the @ is optional and matching is case-insensitive. (2) A PUB…

Output parameters:

- `accuracy_pct` (integer|null): The most flattering and least informative figure here.
- `attribution` (string)
- `calibration` (array)
- `forecaster_kind` (string)
- `generated_at` (string)
- `handle` (string)
- `mean_brier` (number|null): LOWER is better. Do not lead with it - it rewards forecasting only near-certain markets.
- `methodology` (string)
- `note` (string)
- `notice` (string): Set INSTEAD of data when the call succeeded but has nothing to return: unknown slug, empty result, a tool not on this tier, or quota spent. Not an error.
- `provisional` (boolean): When true, report the figures as provisional alongside resolved_forecasts, never as a standing.
- `public_url` (string)
- `publication_threshold` (integer)
- `published` (boolean)
- `ranking_threshold` (integer)
- `requests_remaining_today` (integer|null)
- `resolved_forecasts` (integer): Open forecasts prove nothing; read every figure here against this count.
- `skill_vs_market` (object|null): THE NUMBER TO READ: `brier_skill` above 0 beats the market, about 0 means the forecaster is reproducing it, below 0 is worse.
- `skipseek_score` (number|null): 100 * (1 - mean Brier); inherits the same bias.
- `source` (string)
- `tier` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-skipseek-skipseek/skipseek#diagnostics

## Score history

- 2026-08-21: 59
- 2026-08-20: 59
- 2026-08-19: 59
- 2026-08-18: 59
- 2026-08-17: 59
- 2026-08-16: 59
- 2026-08-15: 59
- 2026-08-14: 59
- 2026-08-13: 59
- 2026-08-12: 59
- 2026-08-11: 59
- 2026-08-10: 58

## Links

- Remote endpoint: https://skipseek.com/mcp
- Website: https://skipseek.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-skipseek-skipseek/skipseek.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-skipseek-skipseek/skipseek.json
- HTML version of this page: https://verifymcp.io/servers/com-skipseek-skipseek/skipseek