# com.skipseek/skipseek

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.3
- **Author:** com.skipseek
- **License:** Unknown
- **Endpoints:** streamable-http https://skipseek.com/mcp
- **Source:** https://skipseek.com
- **Endpoint health:** reachable (last checked 2026-09-20T16:29:51.339Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-20T16:29:51.339Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.
**Findings**
- injection-shaped content (note) in the `list_markets` tool: Links to undeclared domain: skipodds.com

## Tools

9 declared. Observed from a live `tools/list` probe.
- `list_markets` — Browse the SkipSeek board: published prediction markets with the SkipSeek Fair Probability (a cross-venue consensus of every venue trading the same standardized
- `get_market_probabilities` — 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
- `list_discrepancies` — 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 
- `list_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 prob
- `get_market_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-mar
- `list_platforms` — The venues SkipSeek currently publishes: slug, display name, kind (exchange, sportsbook_consensus, poll or model), the reliability weight that venue carries in 
- `get_market_research` — 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, a
- `create_forecast` — 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
- `get_forecaster_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 wh

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"skipseek\": {\n      \"type\": \"http\",\n      \"url\": \"https://skipseek.com/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.skipseek%2Fskipseek
- Install plan: https://forgeregistry.com/api/v1/packages/com.skipseek%2Fskipseek/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.skipseek%2Fskipseek
- HTML page: https://forgeregistry.com/registry/com.skipseek%2Fskipseek
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.
