STATE OF X402 · ISSUE 1 · NOVEMBER 2026

The x402 registry, counted

Every month we count what is actually listed for x402 agents, and publish the count with its method. Not a roundup of announcements — a census, so next month's number means something.

What the registry holds today

348
distinct servers in the registry
683 rows, 335 duplicates collapsed by name
241
with a remote endpoint
69.3% — the rest are install-once packages
8
using safety vocabulary
preflight, guard, policy, spend limit, allowlist
133
servers still on 1.0.0
the most common version, then 0.1.0 at 63

Method

Source: the official MCP Registry, queried in full and deduplicated by server name — 683 rows collapse to 348 distinct servers, because a publisher with twenty versions otherwise takes twenty slots. Snapshot taken 2026-11-15.

“Safety vocabulary” means the description contains one of: preflight, guard, policy, spend control, spend limit, allowlist, allow-list. That is a keyword count, not a quality judgement — it tells you the words are spreading, not whether the checks work.

What we are not claiming

We have measured how many of these endpoints actually respond, but we are not publishing that number yet: it needs two or three months of a stable series before it is worth quoting, and a single sample would be a claim wearing a statistic's clothes. When it is published, the sample size and date will appear beside it, as they do above.

Why count at all

The x402 ecosystem is discussed almost entirely in announcements. A count with a method is falsifiable: if someone says “there are thousands of x402 servers”, they can be checked against this. That is the same reason LIMITS.md exists for the product.

← PayStage · glossary · source