# ClearMarket (remote · api.clearmarket.fyi)

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

- Trust score: 55/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.clearmarket.fyi`: 55/100 (this document), [markdown](https://verifymcp.io/servers/fyi-clearmarket-clearmarket/api.md), [page](https://verifymcp.io/servers/fyi-clearmarket-clearmarket/api)

## Channel facts

- Endpoint: `https://api.clearmarket.fyi/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1503 tokens (~250/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http fyi-clearmarket-clearmarket https://api.clearmarket.fyi/mcp
```

### Codex

```toml
[mcp_servers.fyi-clearmarket-clearmarket]
url = "https://api.clearmarket.fyi/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fyi-clearmarket-clearmarket": {
      "type": "remote",
      "url": "https://api.clearmarket.fyi/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fyi-clearmarket-clearmarket --url https://api.clearmarket.fyi/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fyi-clearmarket-clearmarket:
    url: "https://api.clearmarket.fyi/mcp"
```

### Other

```json
{
  "mcpServers": {
    "fyi-clearmarket-clearmarket": {
      "type": "http",
      "url": "https://api.clearmarket.fyi/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 53, −3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 54, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (6)

### `list_events` (~218 tokens)

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.

Input parameters:

- `category` (string)
- `grade` (string): Resolution Clarity Grade of the primary market.
- `limit` (integer)
- `offset` (integer)
- `platform` (string)
- `q` (string): Free-text search across event questions. Omit to list the whole filtered universe.

### `get_event` (~369 tokens)

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.

Input parameters:

- `detail` (string): concise = essentials only (grade, price, source, also_on per market); full = the complete record. Default full.
- `slug` (string, required): Event slug (e.g. "kxgdpyear-26") or CM event id (CM-EVT-…).

### `get_market` (~299 tokens)

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.

Input parameters:

- `market_id` (string, required): 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` (~94 tokens)

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.

Input parameters:

- `days` (integer)

### `list_signals` (~200 tokens)

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.

Input parameters:

- `category` (string): Signal category tag (case-insensitive): VS_BENCHMARK_DRIFT | CROSS_VENUE_DIVERGENCE | VOLUME_SPIKE | MOMENTUM_REPRICING | PRE_EVENT_PRICING. For thematic filtering use list_events.
- `detection_path` (string)
- `event_id` (string): Return only wires that target or link to this CM event_id.
- `limit` (integer)
- `venue` (string)

### `get_signal` (~111 tokens)

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.

Input parameters:

- `slug` (string, required): Wire slug, e.g. "us-iran-nuclear-deal-before-2027-polymarket-77-2026-05-29".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fyi-clearmarket-clearmarket/api#diagnostics

## Score history

- 2026-08-03: 55
- 2026-08-02: 54
- 2026-08-01: 54
- 2026-07-31: 53
- 2026-07-30: 56
- 2026-07-29: 55
- 2026-07-28: 54
- 2026-07-27: 54
- 2026-07-26: 53

## Links

- Remote endpoint: https://api.clearmarket.fyi/mcp
- Repository: https://github.com/JDSource/clearmarket
- Website: https://clearmarket.fyi/
- Changelog RSS feed: https://verifymcp.io/servers/fyi-clearmarket-clearmarket/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/fyi-clearmarket-clearmarket/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/fyi-clearmarket-clearmarket/api