Every registry, one neutral index

Agenstry federates from every major A2A + MCP registry — including the cloud-vendor registries that lock in their tenants. We're the Switzerland between AWS, Google Cloud, Microsoft, Anthropic, and the community standards bodies. Cross-cloud routing only works if there's a neutral index.

Total federated
56,906
agents + MCP servers indexed
A2A agents
2,629
across 19 sources
MCP servers
54,277
from 13 registries · by 6,824 publishers

Per-source counts below can overlap — one agent often appears in multiple sources (e.g. a2aregistry + GitHub code + crt.sh). The headline above is the count of distinct domains.

Per-source breakdown

Top 25 sources by indexed count. The long tail (individual GitHub forks, single-repo MCP authors) is rolled into the "other sources" row at the bottom of each table.

A2A sources

recrawl_warm850
agentic_market798
mcp_registry719
recrawl_hot659
lists444
github_code425
recrawl_cold260
manifests174
registry151
github_topics131
smithery65
a2aregistry50
crtsh38
seeds8
cdp_discovery4
submitted3
erc80042
ct2
huggingface_spaces1

MCP sources

glama18,636
pypi7,847
docker5,702
mcp.so3,569
npm2,837
n8n2,471
x4021,179
pulsemcp958
io.github.pipeworx-io443
ai.smithery263
jsr233
io.github.csoai-org209
x402/eruditepay-tron122
x402/eruditepay-base108
eu.ansvar105
io.github.br0ski777101
com.mcparmory76
io.tooloracle61
io.github.srotzin60
io.github.codespar57
io.github.lazymac2x54
io.github.daedalus49
io.github.ryudi8449
io.github.theyahia49
x402/scoutgate47
6,812 other sources8,992

Federation sources

Community + standards

A2A community registries

MCP registries

Anthropic + community MCP

Cloud-vendor registries

AWS · Google · Microsoft · Cloudflare

Code + package ecosystems

GitHub · npm · PyPI · Docker

  • GitHub topics: a2a-agent, a2a-protocol, mcp-server
  • GitHub code search: well-known/agent-card.json
  • npm: @modelcontextprotocol/* + community MCP packages
  • PyPI: mcp-* packages
  • Docker Hub: mcp/* images
Curated awesome lists

7 community-maintained README crawls

  • pab1it0/awesome-a2a
  • sing1ee/a2a-directory
  • ai-boost/awesome-a2a
  • punkpeye/awesome-mcp-servers
  • wong2/awesome-mcp-servers
  • appcypher/awesome-mcp-servers
  • modelcontextprotocol/servers
Long-tail discovery

Certificate Transparency + manifests

  • Certspotter CT logs — domains issuing TLS certs with agent-related names
  • crt.sh — keyword-matched certificates
  • Manifest expansion — well-known paths on every discovered domain
Business-identity registries

8 authoritative registries

  • GLEIF (global LEI)
  • UK Companies House
  • Netherlands KvK
  • Australia ABN Lookup
  • Germany Handelsregister
  • EU BRIS network
  • Canada Federal Corporations
  • USA OpenCorporates

Used for the verified-business badge — see /api/registries.

Why neutral federation matters

Each cloud-vendor registry is, by design, scoped to its tenants. AWS won't index agents that live in Google Cloud; Microsoft won't surface those that live in AWS. As intra-cloud A2A adoption grows, the agent web fragments along the same lines as today's email-vs-Slack-vs-Teams divide.

Agenstry is structurally neutral: we don't host runtime, we don't sell cloud capacity, we don't compete with any vendor for tenants. Counterparty agents in any cloud can rely on us as the cross-cloud directory + trust layer without picking sides. Network effects flow to the only neutral index.

Live coverage funnel

For a real-time per-source breakdown of how many candidate URLs each federation source surfaces, how many become valid agent cards, and how many respond to live JSON-RPC, see the compliance funnel.

Are we missing your registry?

Agenstry ships open-source adapters under app/crawler/ and app/registries/. New registries plug in with a single file implementing the RegistryAdapter interface. Open a PR or email hello@agenstry.com.