Tickerz

Name: Tickerz
Author: com.tickerz

MCP serverMCP

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

by com.tickerzhomepage ↗v1.0.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"tickerz","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability13/13 checks ok

30 days ago

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	220 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 16 tools
8 h ago	mcp initialize	ok	200	211 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 16 tools
15 h ago	mcp initialize	ok	200	576 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 16 tools
22 h ago	mcp initialize	ok	200	307 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 16 tools
29 h ago	mcp initialize	ok	200	380 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	200 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	183 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	1409 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 15 tools
2 d ago	mcp initialize	ok	200	1022 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 15 tools
3 d ago	mcp initialize	ok	200	333 ms	server tickerz 1.0.0 · protocol 2025-06-18 · 14 tools

Tools observed via MCP handshake

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. C
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
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 af
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
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", answ
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 Activi
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."
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
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 Ameri
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,
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,
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 lin
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, ca
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, statu
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 pe
methodology — Public Sigma-1 methodology as text (same disclosure as https://tickerz.com/methodology). No proprietary parameters. The text content is Markdown; structuredCont

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.tickerz/tickerz

first seen 4 d ago · fetched 12 h agoopen ↗

Field history (6 recent events)

4 d ago · declared · summary → "Daily indexes of what people do, from public data. On-chain in Bitcoin, so nobody can edit them."
4 d ago · declared · description → "Daily indexes of what people do, from public data. On-chain in Bitcoin, so nobody can edit them."
4 d ago · declared · publisherName → "com.tickerz"
4 d ago · declared · homepageUrl → "https://tickerz.com/connect"
4 d ago · declared · version → "1.0.1"
4 d ago · declared · protocols → ["mcp"]

Tickerz

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from