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.
https://api.clearmarket.fyi/mcpWhat its tools do
6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
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
- 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
{
"tools": {}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
6 advertised
list_events
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.
{
"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
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.
{
"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
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.
{
"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
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.
{
"type": "object",
"properties": {
"days": {
"type": "integer",
"default": 30,
"maximum": 365,
"minimum": 1
}
}
}list_signals
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.
{
"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
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.
{
"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
Resources
Not advertised
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.
- 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.
Claude Code
claude mcp add --transport http clearmarket-mcp https://api.clearmarket.fyi/mcpCodex
codex mcp add clearmarket-mcp --url https://api.clearmarket.fyi/mcpCursor
{
"mcpServers": {
"clearmarket-mcp": {
"url": "https://api.clearmarket.fyi/mcp"
}
}
}Cline
{
"mcpServers": {
"clearmarket-mcp": {
"type": "streamableHttp",
"url": "https://api.clearmarket.fyi/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"clearmarket-mcp": {
"type": "http",
"url": "https://api.clearmarket.fyi/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http clearmarket-mcp https://api.clearmarket.fyi/mcpClaude Desktop
https://api.clearmarket.fyi/mcpWindsurf
{
"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.
Other data and analytics servers
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.