All servers · Crypto & blockchain · Markets & trading · Maps, location & weather

Tickerz

com.tickerz/tickerz · v1.0.1

Measured by MCP Station

Description written by the publisher, not verified

Daily indexes of what people do, from public data. On-chain in Bitcoin, so nobody can edit them.

Connect

claude mcp add --transport http tickerz https://tickerz.com/mcp

{
  "mcpServers": {
    "tickerz": {
      "url": "https://tickerz.com/mcp"
    }
  }
}

Tools as reported by the server

• board
  Use when someone asks what is unusual in crypto or US stocks right now, which coins trade far above their normal volume today, or how many are moving at once. Current Tickerz Terminal: all tracked assets with the 24h move, the activity score as score (0-100; score_1h is one hour earlier) and vol_mul
• asset
  Use when someone asks about one coin or stock: why $X is moving, whether its volume is unusual, how its past spikes turned out, or where it trades. One asset in depth: latest snapshot, scores_30d (30 days of readings, every fourth stored tick, hourly), the open event and the 10 most recent past even
• base_rate
  Use when someone asks what usually happens after a spike like the one an asset shows today, or whether moves like it tend to fade. What historically happened after a move like this asset's current one. Uses 3,213 crypto attention spikes on 175 coins since 2022, found with the live score's formula, m
• receipts
  Use when someone asks how past attention spikes turned out, or wants a track record they can check, losses included. Closed events, newest first, each with its 24h, 7d and 30d receipts (forward return, or null until due; benchmark is BTC for crypto and SPY for stocks, with benchmark_ret_pct over the
• open_questions
  The referee's questions still waiting on their answer: one on-chain attention question per crypto event, "$SYM reads 40 or more at <event open + 24h> UTC", answered at_or_above (40 or more) or below (Under 40). Each carries the score and volume multiple at open, the three nulls frozen at creation (b
• get_question
  One question by id, open or resolved: the statement, the nulls, Tickerz's answer, the crowd split once answers have closed, the outcome (the first stored Activity score at or after the resolve time; void when none lands within 3 hours) and who was right. proofs[] holds each OpenTimestamps proof: the
• arena
  The Arena: predict the number an index lands on. Each index that takes calls has one open question on its next period ("$MINTS for Sep 24. Forecast the number."), with the level it is called against, the forecast count and when forecasts close (when the period called begins). recent: closed question
• submit_forecast
  Two kinds of forecast. 1) Arena (numeric): send question_id as an Arena id from the arena tool (e.g. mints-2026-09-24) or ticker (e.g. MINTS), plus handle (3 to 20 letters, digits or underscores) and value (a number in the index's unit). A handle is claimed by the address that first uses it; the fir
• list_indices
  Use when someone asks how many memecoins launched on pump.fun, what memecoin launchpads earned in fees, how much traded on Kalshi and Polymarket, how many Americans filed first jobless claims, how many paid calls wallets made over x402 on Base and what each cost, or what the US jobs number, unemploy
• get_index
  Use for the history, rules, source and proof of one index named by list_indices (LAYOFFS, YESNO, TRENCHES, MINTS, GIGS, WAGE, JOBS, UNEMP, CPI, CORECPI). JOBS, UNEMP, CPI and CORECPI are monthly, from the Bureau of Labor Statistics: a day's value is the Bureau's figure now, its settlement_value is t
• get_listing_kit
  Use when someone wants to list, write or settle a prediction market on a Tickerz index. A market on the index's next print, ready to paste, for LAYOFFS, MINTS, GIGS, WAGE: question (one sentence, with {strike} left to fill from strikes), period (the next UTC day, or the week ending the Saturday name
• name_a_number
  Use when someone wants a number counted that Tickerz does not publish yet, or a market needs a number nobody sells. Send counts (what should be counted, one line, 3 to 160 characters), optionally source_url (where it can be read) and ticker (2 to 12 letters or digits). Tickerz reads the source's ter
• get_rule
  Use when someone needs to know exactly how a Tickerz index is counted before relying on it: the machine-readable rule (source, query, transform, aggregation, cadence, unit, decimals, precision, revision policy, grade, and settlement rights with the terms page and the quoted clause), its version, and
• get_report
  Use when a contract, a venue or a person needs the signed Tickerz print for an index: the report (ticker, period, value as a scaled integer with decimals, status provisional, final or corrected, rule version and hash, the provider reads with their snapshot hashes, settleable), its hash, the publishe
• list_feeds
  Use when a contract, a venue or a person wants every Tickerz oracle feed at once, as on https://oracle.tickerz.com: per index the newest signed value and its period, status (signed, recounted, final, corrected or disputed), how often it is signed, whether a market may settle on it and why, how many
• methodology
  Public Sigma-1 methodology as text (same disclosure as https://tickerz.com/methodology). No proprietary parameters. The text content is Markdown; structuredContent carries the same text as JSON (model, url, markdown, and its sections as heading and text) for clients that parse JSON.

Website · JSON · Text for agents · Registry updated 2026-10-04