fyi.clearmarket/clearmarket

Est-ce que fyi.clearmarket/clearmarket est sûr ?

Au dernier audit MCP Hub, le serveur MCP « fyi.clearmarket/clearmarket » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• get_event≈ 460 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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "get_event", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_market≈ 342 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • market_id · string · requis
    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).

  Exemple d'appel

  {"name": "get_market", "arguments": {"market_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_signal≈ 137 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Wire slug, e.g. "us-iran-nuclear-deal-before-2027-polymarket-77-2026-05-29".

  Exemple d'appel

  {"name": "get_signal", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_events≈ 339 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.

  Paramètres, retour & exemple (6)

  Paramètres

  • q · string · optionnel
    Free-text search across event questions. Omit to list the whole filtered universe.
  • grade · string · optionnel · A | B | C
    Resolution Clarity Grade of the primary market.
  • limit · integer · optionnel
  • offset · integer · optionnel
  • category · string · optionnel · economics | financials | crypto | companies | technology | politics | geopolitics | health
  • platform · string · optionnel · kalshi | polymarket

  Exemple d'appel

  {"name": "list_events", "arguments": {"q": "texte", "grade": "A", "limit": 1, "offset": 1, "category": "economics", "platform": "kalshi"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_signals≈ 279 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.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
  • venue · string · optionnel · kalshi | polymarket
  • category · string · optionnel
    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 · string · optionnel
    Return only wires that target or link to this CM event_id.
  • detection_path · string · optionnel · news_cycle | cross_venue_divergence | benchmark_drift | volume_spike

  Exemple d'appel

  {"name": "list_signals", "arguments": {"limit": 1, "venue": "kalshi", "category": "texte", "event_id": "texte", "detection_path": "news_cycle"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_upcoming_catalysts≈ 133 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • days · integer · optionnel

  Exemple d'appel

  {"name": "list_upcoming_catalysts", "arguments": {"days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.clearmarket.fyi/mcp