AgentIndex · about the index
About the Index
What we count, how we check it, and what each number does and does not mean. Everything on this page is regenerated from the live database.
Live Updated 2026-09-01 06:32 UTC
The brief
Where the index stands today
What nobody else shows
The verification gap
Directories list what publishers say. We probed every domain that declares an MCP server and recorded what actually answered. Of 10,053 declared endpoints:
- Confirmed live4,22442.3%Answered a real JSON-RPC initialize handshake
- Claimed, did not answer3,68236.9%Listed as MCP but returned no valid handshake
- Robots-blocked1,40414.1%We honour robots.txt and did not probe these
- Unreachable6776.8%DNS or connection failure at probe time
Coverage
Endpoint domains by protocol
Counted from live protocol detection and authoritative registries. A domain can speak more than one protocol.
Browse by protocol
Every resource carries the protocols we detected on it. Pick one to filter the index.
Or explore everything — filter by protocol or category, then open any agent for its live tool list.
Composition
Largest resource types
How to read this
The caveats that travel with the numbers
- Resource counts are concentration-skewed: a few hosts bulk-list thousands of endpoints.
- 1,404 domains are counted but never probed — we honour robots.txt.
- The verification funnel is a magnitude comparison, not a trend. We keep roughly three days of probe history, which is not enough to draw a line through.
- A domain can speak more than one protocol, so the protocol bars sum to more than the number of domains.
Full method: Methodology · machine-readable: /data.json · crawl policy: crawler-policy