Every figure below is the sentence the matching Sato Hub numbers page is serving right now, quoted as it stands, with the week-over-week change of the same series beside it. Nothing here is restated in different words, and nothing is carried over from a previous week: a series with one reading shows "no prior reading" rather than a change of zero. Readings are as of 2026-11-16.
Agents registered on ERC-8004, by chain
Registered agents per chain: 0G 3,941,233, Base 1,198,611, BNB Chain 419,511 and 23 more chains; chains are never added together, as of 2026-11-16.
| What | This week | Change on last week | |---|---|---| | 0G | 3,941,233 registered | no prior reading — one weekly reading banked so far | | Base | 1,198,611 registered | +43,069 | | BNB Chain | 419,511 registered | +24,057 | | Ethereum | 56,540 registered | +872 | | Robinhood Chain | 25,997 registered | +11,017 | | Optimism | 22,084 registered | +4 | | Abstract | 16,919 registered | no prior reading — one weekly reading banked so far | | X Layer | 15,949 registered | no prior reading — one weekly reading banked so far |
Method, coverage and the chains or pairs behind this figure: https://satohub.ai/numbers/erc-8004-agents-by-chain. Measured against ERC-8004 — Trustless Agents (the EIP), ERC-8004 reference implementation.
x402 payment endpoints that actually answer
15 of the 16 x402 payment endpoints we reached replied with valid payment terms; nothing was paid, as of 2026-11-16.
| What | This week | Change on last week |
|---|---|---|
| Paid resources (named in a /.well-known/x402 manifest) answering a parseable HTTP 402 | 15 | no prior reading — the probe is a point-in-time run, not a banked weekly series |
| x402 sellers registered (venue stage selling) | unknown | no prior reading — one weekly reading banked so far |
| x402 settlements observed (venue stage settling) | unknown | no prior reading — one weekly reading banked so far |
Method, coverage and the chains or pairs behind this figure: https://satohub.ai/numbers/x402-endpoints-that-answer. Measured against x402 — protocol specification, RFC 9110 §15.5.3 — HTTP 402 Payment Required.
Listed crypto MCP servers that answered a handshake
57 of 91 listed crypto MCP servers answered and listed their tools without a key; 26 asked for a key and 8 did not connect, as of 2026-11-16.
| What | This week | Change on last week |
|---|---|---|
| Endpoints that answered initialize + tools/list anonymously | 57 | no prior reading — a daily point-in-time check of other people's servers, not a banked weekly series |
Method, coverage and the chains or pairs behind this figure: https://satohub.ai/numbers/mcp-servers-that-answer. Measured against Model Context Protocol — the initialize handshake.
Score movers
Across 496 listings carrying a Sato Score on both days between 2026-11-09 and 2026-11-16, 8 rose and 8 fell, 8 crossed a tier boundary, and 3 were scored for the first time. Every reading is a daily snapshot; a day nobody measured is a gap and is never carried forward, and the Sato Score is how open, active and verifiable a project is — not a safety, quality or returns grade.
| What | This week | Change on last week | |---|---|---| | Monad Agent Kit | 69 (Medium) | +30 · maintenance 5→35 | | Algorand MCP | 83 (High) | +15 · maintenance 20→35 | | create-solana-agent | 56 (Medium) | +15 · maintenance 5→20 | | MOSS Agent Skills Pack | 50 (Medium) | -12 · maintenance 25→13 | | TensorFeed x402 Base MCP | 64 (Medium) | -11 · maintenance 35→25 | | NEAR Shade Agent Framework | 67 (Medium) | -11 · maintenance 35→25 |
Method, coverage and the chains or pairs behind this figure: https://satohub.ai/movers. Measured against Monad Agent Kit — the project's own source, Algorand MCP — the project's own source, create-solana-agent — the project's own source, MOSS Agent Skills Pack — the project's own source.
What arrived in the directory
7 listings were added to the Sato Hub directory and 54 published a release in the last 7 days, as of 2026-11-16: 402cron, 402post, 402registry, Canvas64, SellTape MCP, Siebly Agent Skills. Each is an observed event with a date and a link to its own source, never an endorsement.
The rows, with the source for each: https://satohub.ai/launches.
What we corrected
Over the last 6 months Sato Hub added 359 listings and retired 3, recorded 0 verification changes, applied 3 corrections from 0 verified claims, and decided 61 submissions. The ledger behind that sentence, month by month, is at https://satohub.ai/transparency.
How to check any of this
Every figure above is derived at page-render time from Sato Hub's own tables and from public chain and registry reads. The free catalogue export is at https://satohub.ai/api/export/index.json and the current-week adoption rows at https://satohub.ai/api/export/adoption.json, both CC-BY-4.0. Over MCP: onchain_agent_get_metrics, onchain_agent_get_trend and onchain_agent_explain_number, which returns the method for any of these.
A figure here is never summed across venues, chains or stages — those rows do not add — a sampled rate is never multiplied by a population, and an unknown is an unknown, never a zero.