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
159,265
agents + MCP servers indexed
A2A agents
7,287
across 39 sources
MCP servers
151,978
from 13 registries · by 17,388 publishers

Per-source counts below can overlap, as 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_hot3,420
agentic_market2,962
recrawl_warm2,649
mcp_registry1,747
cdp_discovery1,440
manifests1,105
github_code814
lists483
x402_list447
registry368
recrawl_cold290
n8n_workflows194
github_topics155
a2a_registry_org138
a2aregistry114
smithery89
mpp87
submitted65
pay_sh49
crtsh38
erc800436
sitemap29
resalvage-20260817b21
resalvage-2026081721
a2a-validate15
14 other sources64

MCP sources

glama79,306
pypi9,682
docker8,134
n8n6,953
npm6,777
pulsemcp4,474
mcp.so3,604
x4023,024
io.github.pipeworx-io1,313
direct1,252
io.github.mcp-dir1,098
io.github.evozim375
io.github.csoai-org330
jsr318
docker-mcp271
ai.smithery214
x402/scoutgate214
io.github.codespar127
app.wishpool125
io.github.cyanheads125
io.github.wxt-ai122
x402/eruditepay-tron122
composio113
x402/eruditepay-base111
eu.ansvar110
17,376 other sources23,684

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's public index and rankings are structurally neutral: we don't sell placement, cloud capacity, or preferential scores. We do offer a separately labelled managed-agent product, but hosted agents receive no ranking advantage and are measured under the same published methodology. Counterparty agents in any cloud can therefore use the cross-cloud evidence layer without a registry or payment rail deciding what they see.

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. To add one, email hello@agenstry.com with the registry's API and we will write the adapter.