Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 699 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Other
Reference data for prediction markets: graded resolution clarity, cross-venue links, provenance.
2 failed · 7 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 1 | 0 | 3 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 2 | 2 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using ClearMarket
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http clearmarket https://api.clearmarket.fyi/mcpCapabilities
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.
DiscoveredFetch 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.
DiscoveredFetch 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.
DiscoveredBrowse 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.
DiscoveredBrowse 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.
DiscoveredList 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 96 ms | 6 | |
| Connected | 49 ms | 6 |