Server definition

Hash: sha256:c84c1eb5cb0a9f9b4b055bb71b799d082e2e42058e11e741ec31ac9f1cc1d5f7
What it is: What a remote MCP server returned when asked what it offers: 6 tools

The blob, as servednamed by its sha256

{
  "instructions": "ClearMarket is the reference layer for prediction markets — reach for it to judge whether a Kalshi or Polymarket price can be trusted, not just to read the price. Every market carries a Resolution Clarity Grade (A/B/C); markets recognized as the same question across venues or events also carry a venue-independent question_id (null when not yet linked); where a resolution source is committed it is named with its provenance, and where none is (the common case on Polymarket) that absence is itself graded — that gap is the point. Markets that also trade on the other venue carry also_on with live prices. Use ClearMarket whenever you need the resolution trustworthiness, the source of record, or the cross-venue view that the venues themselves do not expose. Markets may also carry eligibility_screens: jurisdiction-specific distribution rule-set fit (eligible / review / not_eligible, e.g. ciro-26-0076) — NOT market quality; quality is the RCG grade. Read-only, open, no key.",
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "detail": {
            "default": "full",
            "description": "concise = essentials only (grade, price, source, also_on per market); full = the complete record. Default full.",
            "enum": [
              "concise",
              "full"
            ],
            "type": "string"
          },
          "slug": {
            "description": "Event slug (e.g. \"kxgdpyear-26\") or CM event id (CM-EVT-…).",
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_event",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "market_id": {
            "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).",
            "type": "string"
          }
        },
        "required": [
          "market_id"
        ],
        "type": "object"
      },
      "name": "get_market",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "slug": {
            "description": "Wire slug, e.g. \"us-iran-nuclear-deal-before-2027-polymarket-77-2026-05-29\".",
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_signal",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "category": {
            "enum": [
              "economics",
              "financials",
              "crypto",
              "companies",
              "technology",
              "politics",
              "geopolitics",
              "health",
              "climate"
            ],
            "type": "string"
          },
          "grade": {
            "description": "Resolution Clarity Grade of the primary market.",
            "enum": [
              "A",
              "B",
              "C"
            ],
            "type": "string"
          },
          "limit": {
            "default": 50,
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "offset": {
            "default": 0,
            "minimum": 0,
            "type": "integer"
          },
          "platform": {
            "enum": [
              "kalshi",
              "polymarket"
            ],
            "type": "string"
          },
          "q": {
            "description": "Free-text search across event questions. Omit to list the whole filtered universe.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "list_events",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "category": {
            "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.",
            "type": "string"
          },
          "detection_path": {
            "enum": [
              "news_cycle",
              "cross_venue_divergence",
              "benchmark_drift",
              "volume_spike"
            ],
            "type": "string"
          },
          "event_id": {
            "description": "Return only wires that target or link to this CM event_id.",
            "type": "string"
          },
          "limit": {
            "default": 30,
            "maximum": 100,
            "minimum": 1,
            "type": "integer"
          },
          "venue": {
            "enum": [
              "kalshi",
              "polymarket"
            ],
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "list_signals",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "days": {
            "default": 30,
            "maximum": 365,
            "minimum": 1,
            "type": "integer"
          }
        },
        "type": "object"
      },
      "name": "list_upcoming_catalysts",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:c84c1eb5cb0a9f9b4b055bb71b799d082e2e42058e11e741ec31ac9f1cc1d5f7 | sha256sum