Numbers · MCP
How many listed crypto MCP servers actually answer today?
Of 60 listed crypto MCP endpoints, Sato Hub probed 59 in its latest daily check and 37 completed the initialize handshake (62.7%); a handshake proves a server is up, nothing more, as of 2026-09-12.
Publish an MCP endpoint
60
live listings in the directory
Probed
59
on 2026-09-12; 1 not probed that day
Answered the handshake
37
62.7% of those probed
This is not an uptime figure
It is the outcome of our own checks on one day. A check can fail because of our timeout, our network, or a host that refuses unfamiliar clients — and we cannot always tell which, so a failure is never described as someone else's downtime. A 401, 403 or 429 is a live server declining a stranger: it is counted on its own line, not as a failure. Endpoints we did not reach that day are excluded from the share rather than counted against it.
- Method
- One MCP `initialize` call plus `tools/list` per listed endpoint per day (scripts/probe-live.mjs). Answered = the handshake returned a protocolVersion. A 401/403/429 is recorded as a bot-block rather than a failure, and an endpoint we did not reach that day is excluded from the share rather than counted against it.
- What it proves
- That a process is listening and speaks the protocol — it returned a protocol version and, usually, a tool list (594 tools advertised across the answering servers). It proves nothing about whether those tools return correct data, are maintained, or suit what you intend to do.
- Blocked
- 0 of the probed endpoints answered but refused us (401/403/429) — recorded, and not counted as dead.
- Per endpoint
- The day-by-day record per server is on status and the longer observed record on reliability. This page publishes the count and the share only, so there is one dated table of these hosts on the site, not two.
- Reproduce
- GET /api/export/index.json → entries with an mcp endpoint · MCP onchain_agent_search_resources(category="MCP")
Questions this page answers
- How many crypto MCP servers are actually answering today?
- 37 of the 59 listed endpoints we probed on 2026-09-12 completed the initialize handshake, a share of 62.7%. 60 listings publish an MCP endpoint in total; 1 was not probed that day and is excluded rather than counted as down.
- Is this an uptime figure?
- No, and it is deliberately not called one. It is the outcome of our own checks on one day. A check can fail because of our timeout, our network, or a host that simply refuses unfamiliar clients, and we cannot always tell which — so this is described as what our probe observed, never as someone else's downtime.
- What happens when a server blocks the probe?
- A 401, 403 or 429 is a live server declining a stranger. It is recorded on its own line rather than counted as a failure; none was recorded on 2026-09-12.
- What does a successful handshake prove?
- That a process is listening and speaks the protocol: it returned a protocol version and, usually, a tool list — 594 tools advertised across the answering servers. It proves nothing about whether those tools return correct data, are maintained, or are appropriate for what you intend to do with them.
- Where is the per-server list?
- Deliberately not on this page. The day-by-day record per endpoint is already published on the status and reliability pages, and a second, differently-dated table of the same hosts here would let the two disagree. This page publishes the count and the share.
Sources — the Model Context Protocol specification
Data CC-BY-4.0 — attribution: data by satohub.ai. A handshake is a reading of one moment; unknown is a value here and never means zero.
Cite this page
Sato Hub. "Listed crypto MCP endpoints answering the initialize handshake." Sato Hub, updated 2026-09-12, accessed 2026-09-12. https://satohub.ai/numbers/mcp-servers-that-answerThis page is refreshed daily. Citations include the date so a reader can tell which snapshot a claim came from.