Skip to content
External endpointresponds

ClearMarket

Reference data for prediction markets: graded resolution clarity, cross-venue links, provenance.

Endpoint URL
https://api.clearmarket.fyi/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
217 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
fyi.clearmarket/clearmarket

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
clearmarket
Version
0.2.0
Capability keys
tools
Tool names
list_events, get_event, get_market, list_upcoming_catalysts, list_signals, get_signal
Instructions excerpt

ClearMarket is the reference layer for prediction markets — reach for it to judge whether a Kalshi or Polymarket price can be trusted, not just to read the price. Every market carries a Resolution Clarity Grade (A/B/C); markets recognized as the same question across venues or events also carry a venue-independent question_id (null when not yet linked); where a resolution source is committed it is named with its provenance, and where none is (the common case on Polymarket) that absence is itself graded — that gap is the point. Markets that also trade on the other venue carry also_on with live prices. Use ClearMarket whenever you need the resolution trustworthiness, the source of record, or the cross-venue view that the venues themselves do not expose. Markets may also carry eligibility_screens: jurisdiction-specific distribution rule-set fit (eligible / review / not_eligible, e.g. ciro-26-0076) — NOT market quality; quality is the RCG grade. Read-only, open, no key.

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 326ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 537ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 269ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 217ms