Koskamo

ClearMarket MCP

Provides agents with read-only access to normalized prediction market data from Kalshi and Polymarket. It offers tools to browse events, retrieve market prices and resolution provenance, check upcoming catalysts, and access the CM Signal wire, all using a unified schema with graded resolution clarity.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

ClearMarket MCP logo, by ClearMarketVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by ClearMarket
MCP endpoint (Streamable HTTP)
https://api.clearmarket.fyi/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

6 of 6 have a description · 0 of 6 declare behavior hints · 3 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to clearmarket.fyi ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Browse and search prediction market events by keyword or category
  • Retrieve detailed market prices and resolution source provenance
  • List upcoming catalysts for specified events
  • Access the CM Signal wire for market intelligence

Source and maintenance

Vendor evidenceRegistry 0.2.0
Maintenance checked

Protocol and capabilities

Server
clearmarket 0.2.1
MCP protocol negotiated in check
2025-06-18
Tools
6 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

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.

Tools

6 advertised

list_events
Advertised by the server during the last successful anonymous check.

Browse or search ClearMarket prediction-market events. Filter by category, platform, Resolution Clarity Grade, or free-text `q`. `q` is token-AND across question + tags, so SHORT KEYWORD queries match best ("microstrategy bitcoin", "fed rate") — natural-language phrases often return nothing. Returns compact graded summaries: slug, question, venues_covered, primary grade, rcg_score (0-100, for ranking clarity), last_price, and status (open / resolved). Start here when you have a topic but not a slug; then call get_event for the full graded record. Categories: economics, financials, crypto, companies, technology, politics, geopolitics, health, climate.

list_events input schema
{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Free-text search across event questions. Omit to list the whole filtered universe."
    },
    "grade": {
      "enum": [
        "A",
        "B",
        "C"
      ],
      "type": "string",
      "description": "Resolution Clarity Grade of the primary market."
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 100,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0
    },
    "category": {
      "enum": [
        "economics",
        "financials",
        "crypto",
        "companies",
        "technology",
        "politics",
        "geopolitics",
        "health",
        "climate"
      ],
      "type": "string"
    },
    "platform": {
      "enum": [
        "kalshi",
        "polymarket"
      ],
      "type": "string"
    }
  }
}
get_event
Advertised by the server during the last successful anonymous check.

Fetch the full ClearMarket record for one event by slug: the canonical question, every market in this event's single-venue bundle, each market's current price + Resolution Clarity Grade (A/B/C) + resolution-source provenance, the canonical question_id where the question is linked across venues/events (null otherwise; also_on lists the same question priced on the other venue, when it trades there), and the upcoming catalyst dates that move it before it resolves. In the default detail="full", each market in the bundle is FULLY detailed (grade, rcg.caps, provenance, direction, settlement_style, also_on) — you do not need a separate get_market call for markets already in this event. Note: a shared question_id means same topic across venues; in rare cases it links structurally-different contracts (e.g. a "hike" vs a "cut-count" market), so verify the contract shape before treating two as an arbitrage pair. Use when you need the authoritative, graded view of a SPECIFIC event — including its cross-venue twins via also_on — before reasoning about or acting on a prediction market. If you only have a topic (not a slug), call list_events first. Set detail="concise" for a quick grade/price/source check (each market trimmed to the essentials — much smaller for events with many markets); use the default detail="full" when you need every market's rules, contract shape, and complete provenance.

get_event input schema
{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Event slug (e.g. \"kxgdpyear-26\") or CM event id (CM-EVT-…)."
    },
    "detail": {
      "enum": [
        "concise",
        "full"
      ],
      "type": "string",
      "default": "full",
      "description": "concise = essentials only (grade, price, source, also_on per market); full = the complete record. Default full."
    }
  }
}
get_market
Advertised by the server during the last successful anonymous check.

Fetch one market and judge whether its price can be trusted. Accepts whatever id you have: a ClearMarket id (CM-MKT-…), a venue-native market id or Kalshi ticker, or a market URL (best-effort — Kalshi tickers / a native id in the path resolve; for Polymarket pass the conditionId, not the slug URL). Returns: raw question, current price / implied probability, the Resolution Clarity Grade with rcg.score (0-100) and rcg.caps (a cap such as "uncommitted_placeholder" hard-limits the grade — that is why a single-source market can still be C), full resolution provenance (arbitration_model = who resolves it, named source, source_type, and a graded source_status on EVERY market: named / no-committed-source / none / unknown), the contract shape (direction, settlement_style, threshold), the canonical question_id where linked, and also_on (the same question priced on other venues). The returned market_id is ALWAYS the canonical ClearMarket id (CM-MKT-…) — store and reuse THAT, not the venue id. Use before trusting or acting on a price.

get_market input schema
{
  "type": "object",
  "required": [
    "market_id"
  ],
  "properties": {
    "market_id": {
      "type": "string",
      "description": "A ClearMarket id (CM-MKT-…), a venue-native market id / Kalshi ticker, or a market URL (best-effort: Kalshi URLs resolve; for Polymarket pass the conditionId)."
    }
  }
}
list_upcoming_catalysts
Advertised by the server during the last successful anonymous check.

List scheduled catalysts (CPI, jobs, FOMC, GDP, large-cap earnings) in the next N days that move prediction-market prices BEFORE those markets resolve — a cross-event view across the whole calendar. Each entry is provenanced to its authoritative source (BLS, Fed, etc.). Use to find what scheduled events will reprice the prediction-market universe soon.

list_upcoming_catalysts input schema
{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "default": 30,
      "maximum": 365,
      "minimum": 1
    }
  }
}
list_signals
Advertised by the server during the last successful anonymous check.

Browse the CM Signal daily wire — short, structured prediction-market bulletins (the price is the lede, news is context). Filter by event_id (every wire touching a specific event), category, venue, or detection type (news_cycle, cross_venue_divergence, benchmark_drift, volume_spike). Returns compact records, newest first; call get_signal for the full bulletin. Use to find ClearMarket's editorial read on what is moving.

list_signals input schema
{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 30,
      "maximum": 100,
      "minimum": 1
    },
    "venue": {
      "enum": [
        "kalshi",
        "polymarket"
      ],
      "type": "string"
    },
    "category": {
      "type": "string",
      "description": "Signal category tag (case-insensitive): VS_BENCHMARK_DRIFT | CROSS_VENUE_DIVERGENCE | VOLUME_SPIKE | MOMENTUM_REPRICING | PRE_EVENT_PRICING. For thematic filtering use list_events."
    },
    "event_id": {
      "type": "string",
      "description": "Return only wires that target or link to this CM event_id."
    },
    "detection_path": {
      "enum": [
        "news_cycle",
        "cross_venue_divergence",
        "benchmark_drift",
        "volume_spike"
      ],
      "type": "string"
    }
  }
}
get_signal
Advertised by the server during the last successful anonymous check.

Fetch one full CM Signal wire by slug: headline, the 3-5 structured bullets, atomic claims with per-field provenance tiers, the target + linked events, primary and related markets with prices, and sources. Use when you have a wire slug (from list_signals) and need the complete bulletin with its proof chain.

get_signal input schema
{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Wire slug, e.g. \"us-iran-nuclear-deal-before-2027-polymarket-77-2026-05-29\"."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
224 ms
95th percentile latency
224 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 224 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http clearmarket-mcp https://api.clearmarket.fyi/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add clearmarket-mcp --url https://api.clearmarket.fyi/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable clearmarket-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "clearmarket-mcp": {
      "url": "https://api.clearmarket.fyi/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "clearmarket-mcp": {
      "type": "streamableHttp",
      "url": "https://api.clearmarket.fyi/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start clearmarket-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "clearmarket-mcp": {
      "type": "http",
      "url": "https://api.clearmarket.fyi/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http clearmarket-mcp https://api.clearmarket.fyi/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.clearmarket.fyi/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "clearmarket-mcp": {
      "serverUrl": "https://api.clearmarket.fyi/mcp"
    }
  }
}

Let your agent find its tools

Find servers like ClearMarket MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run ClearMarket MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing