mcp server
ClearMarket
Reference data for prediction markets: graded resolution clarity, cross-venue links, provenance.
Description as published by the maintainer. Source
- version 0.2.0
- active
active — Most recent push to the repository was 2026-08-06.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_event(slug, detail)- 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. Required: slug.
get_market(market_id)- 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. Required: market_id.
get_signal(slug)- 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. Required: slug.
list_events(q, grade, limit, offset, category, platform)- 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_signals(limit, venue, category, event_id, detection_path)- 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_upcoming_catalysts(days)- 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.
Last successful function declaration observed on . Source: https://api.clearmarket.fyi/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.clearmarket.fyi/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 3 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 5 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.2.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-09 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-06-09 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.clearmarket.fyi | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | api.clearmarket.fyi |
Where to get it
Related, by what their authors tagged them
-
com.predictionmarketspicks/quant
— last commit 2026-07-27, shares kalshi, polymarket, prediction-markets
Quant tools + an NFL fantasy draft assistant for AI agents — Kalshi & Polymarket EV, edge, ADP.
-
Simmer
— last commit 2026-08-05, shares kalshi, polymarket, prediction-markets
Trade prediction markets with AI agents — skill discovery, autoresearch, and execution.
-
CoinRithm Agent Trading
— last commit 2026-08-06, shares kalshi, polymarket, prediction-markets
Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM.
-
Kalshi Prediction Markets
— last commit 2026-08-05, shares kalshi, prediction-markets
MCP server for Kalshi prediction markets: native RSA-PSS auth, rate limiting, demo/prod safety.
-
Polymarket MCP
— last commit 2026-08-05, shares market-data, polymarket, prediction-markets
Polymarket market data, live CLOB books, replay, simulation, and opt-in trading in Rust.
-
pmq (Polymarket CLOB V2)
— last commit 2026-08-03, shares market-data, polymarket, prediction-markets
Production-proven Polymarket CLOB V2 trading and data. Fail-closed fills; keys stay local.
-
io.github.abm-dev-git/abm-mcp
— last commit 2026-07-30, shares enrichment
abm.dev — the account-based marketing API for AI agents: Search, Enrich, and Create across B2B.
-
Company Enrichment API
— last commit 2026-07-31, shares enrichment
Company firmographics from domain: name, socials, tech stack, emails, phone, address
-
Person Enrichment API
— last commit 2026-07-19, shares enrichment
Person lookup from email: name, title, company, social profiles. x402.
-
Technology Stack Detection API
— last commit 2026-07-31, shares enrichment
Detect 50+ technologies on any website: CMS, frameworks, analytics, CDN. x402.
These share tags the maintainers applied themselves, such as kalshi, polymarket, prediction-markets, market-data. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: enrichment, kalshi, market-data, polymarket, prediction-markets, resolution-logic.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json