Which crypto MCP servers and tools answer most reliably?

Of 432 listings with at least 14 days of record, 333 answered every check, 381 answered at least 95% and 45 fell under 80%. The full ranked table is on this page, each row with its record length and probe method.

No, and it is deliberately not called that. It is the share of OUR daily checks that succeeded. A failure can be their outage, our runner or the network in between, and only the first is a fact about the project — which is why the figure describes a check rather than someone else's availability.

How strong is the evidence behind a row?

It varies, and the row says which. 78 listings are checked with a real MCP initialize-and-tools/list handshake, which a parked domain cannot fake; the rest are a plain HTTP reach, which is weak evidence that anything useful is running. 120 also had their documented install reproduced in a container.

Why are some records marked not established?

Because before 2026-09-01 a bot-block counted as a failure, so where an earlier check failed the rate on that row covers only the checks since that date. Rows whose failures are all unattributable are shown but ranked last rather than quietly scored as if they had failed.

Daily checks

Reliability Index

Name: Sato Hub reliability index
Creator: Sato Hub
License: https://creativecommons.org/licenses/by/4.0/

See which crypto agent tools answered our daily check, ranked by success rate.

See the ranking Get the data

Updated2026-10-22
Minimum record14 days

What it is
The share of our daily checks each tool answered.
How we check
Once a day we try the MCP handshake, or reach the site over HTTP when there’s no MCP endpoint.
How you use it
Shortlist tools that answer reliably. Treat HTTP-only rows as a weaker signal.

Ranked

432

tools with 14+ days of checksas of 2026-10-22

Answered every check

333

of the ranked toolsas of 2026-10-22

Under 80%

of ranked tools with a known causeas of 2026-10-22

MCP-checked

answer a real MCP handshakeas of 2026-10-22

The ranking

354 tools

AnsweredNo answerNo check counted

RankToolAnsweredLast 30 daysOn record

TermiX
Agent MarketplaceHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
50days on recorddays
Maestro (Telegram trading bot)
Trading ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
39days on recorddays
Pons
DeFi ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
39days on recorddays
Pools.trade
DeFi ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
39days on recorddays
RobinPad
DeFi ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
39days on recorddays
AgentSwap
Trading ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
36days on recorddays
Bankless Claimables API
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Galxe Quest API
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
GoPlus AgentGuard
Security ToolHTTP onlyInstall reproduced
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
GoPlus Security
Security ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Honeypot.is
Security ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Okto
Wallet InfrastructureHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Ralio
Payment RailHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Rhea Finance
DeFi ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Vultisig
Wallet InfrastructureHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Webacy
Security ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
WOO X
Trading ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
30days on recorddays
Arc (Circle)
Developer ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Arcus
Trading ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Arkham
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Amazon Bedrock AgentCore Payments
Payment RailHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Chainlink for Agents
API / SDKHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Circle Agent Stack
Wallet InfrastructureHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
ClawRouter (BlockRun)
Developer ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Drip (DripStack)
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Glassnode
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Ledger Agent Stack
Wallet InfrastructureHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Lightning Agent Tools (Lightning Labs)
Skill RepoHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
MadeOnSol
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Massive (formerly Polygon.io)
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
NEAR Intents 1Click API (+ MPP payment method)
API / SDKHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
NOFX
Trading ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
OneSource
Data ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Open Wallet Standard (OWS)
Wallet InfrastructureHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Polymarket Agent Skills
Skill RepoHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Robinhood Chain MCP
MCPHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
NEAR Shade Agent Framework
Agent FrameworkHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Simmer
Trading ToolHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
Stripe Machine Payments
Payment RailHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
TON Agentic Wallets
Wallet InfrastructureHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
You.com API
API / SDKHTTP only
100%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
29days on recorddays
8004Swap
Trading ToolHTTP only
100%
answered
2026-09-2327 answered0 no answer3 no check2026-10-22
27days on recorddays
CoinOS Skills (AiCoin)
Skill RepoHTTP only
100%
answered
2026-09-2326 answered0 no answer4 no check2026-10-22
26days on recorddays
Alby x402 Facilitator
Payment RailHTTP only
100%
answered
2026-09-2325 answered0 no answer5 no check2026-10-22
25days on recorddays
Aperture (L402 proxy, Lightning Labs)
Payment RailHTTP only
100%
answered
2026-09-2325 answered0 no answer5 no check2026-10-22
25days on recorddays
Lightning pi
API / SDKHTTP only
100%
answered
2026-09-2325 answered0 no answer5 no check2026-10-22
25days on recorddays
x402-ping
API / SDKHTTP only
100%
answered
2026-09-2323 answered0 no answer7 no check2026-10-22
23days on recorddays
Yelden (YAAF)
Developer ToolHTTP only
100%
answered
2026-09-2314 answered0 no answer16 no check2026-10-22
14days on recorddays
Aptos MCP
MCPHTTP only
98.9%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
90days on recorddays
Bitget Agent Hub
MCPHTTP onlyInstall reproduced
98.9%
answered
2026-09-2329 answered0 no answer1 no check2026-10-22
90days on recorddays

How to read thisShowHide

This is not uptime. It is the share of our checks that succeeded. A failed check can be their outage, our runner, or the network. Only the first is a fact about the project, and we only started recording which was which on 2026-09-01.
An MCP handshake is strong evidence. An HTTP reach is weak. A parked domain answers HEAD. A tools/list response cannot be faked by a parked domain.
“Answered a test call” is stronger than “answers a handshake”. Each MCP server is asked one read-only call a day, picked from its own tool list: a list_, get_ or search_ name carrying no mutating verb anywhere in it (get_swap_quote is refused despite the prefix), taking no required arguments and declaring none that look like an address, a key or an amount. No pill means we did not ask, never that the server failed. An error is not a verdict either: one common answer is a server telling us an argument it did not mark as required is in fact required, which is the server working.
“Empty tool list” means the handshake succeeded and the server advertised nothing. The endpoint answered, so it counts as answered, but an agent that finds it sees nothing it can call. Servers that need a login can look like this to us.
Before 2026-09-01 a bot-block (HTTP 403) counted as a failure. When an earlier check failed, the rate and the record length on that row cover only the checks since that date (a record with no earlier failure is counted whole), and a listing needs 14 of them to be ranked. Rows whose failures all have an unknown cause are shown but ranked last, marked cause unknown.
Install reproduced means we ran the documented install and entry in a throwaway container, on the date of the check. It says nothing about runtime safety.
The daily bars show the last 30 days, one bar per day. A short grey bar means no check was counted that day: no check ran, or the miss was on our side. It is a gap in our record, not a failure.
Colours group the number, they do not grade it. 95% and up, 80% to under 95%, and under 80%. Grey means the cause of every miss is unknown.

Take the data. JSON or CSV (CC-BY), with the columns observed_success_pct, observed_days and install_verified_at. Over MCP: search_resources(min_observed_success).

How long tools stay activeShowHide

133 days of daily records, 493 tools. One record per tool per day. A tool enters a table only if it was Active at its first record and has been observed for the full window. Otherwise it is left out, not counted as surviving.

Stopped being Active within

Window	n	No longer Active	Share
30 days	101	24	23.8%
60 days	95	31	32.6%
90 days	95	30	31.6%

In this table, Active = a commit, release or post within 30 days, applied on each record's own date (listing badges count commits and releases only). Leaving Active is the event. Whether a tool later becomes Quiet (over 90 days) or Dormant (over a year) takes longer than most of this record.

Still Active at day 90, by feature

Feature	With (n)	Without (n)
Has an MCP endpoint	not enough data (n<20) (11)	70.2% (84)
Install reproduced in a container	69.2% (52)	67.4% (43)
≥3 provenance-stamped fields	69.2% (78)	not enough data (n<20) (17)

Association, not cause. Listings that already had an MCP endpoint, a verified install or rich provenance were also the ones with more engaged maintainers; the table cannot separate the two.

Still Active at 30 / 60 / 90 days, by month added

Month added is the month a tool entered our daily records, not the project's age. Of the tools Active at their first record, the share still Active N days later. A tool not yet observed for the full N days is left out of that column, so a young month fills in from the left as the record grows.

Month added	Entered	Active at first record	Day 30 (n)	Day 60 (n)	Day 90 (n)
2026-06	132	46	80.4% (46)	78.3% (46)	78.3% (46)
2026-07	241	49	69.4% (49)	57.1% (49)	59.2% (49)
2026-08	2	0	not yet observed	not yet observed	not yet observed
2026-09	67	26	not enough data (n<20) (6)	not yet observed	not yet observed
2026-10	51	21	not yet observed	not yet observed	not yet observed

Association, not cause. The cohort is the month a listing entered OUR snapshot series, not the project's age; "Active" is our liveness rule (activity within 30 days on the snapshot's own date), not the project's word. A listing not observed for the full window is excluded, not counted either way.

As of 2026-10-22.

Reference

QuestionsWhat people ask about this pageShowHide

SourcesWhere the data comes fromShowHide

Cite this pagePlain text, APA or BibTeXShowHide

Cite this page

Sato Hub. "Sato Hub reliability index." Sato Hub, updated 2026-10-22, accessed 2026-10-22. https://satohub.ai/reliability

Data last refreshed 2026-10-22; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.