Live · updated daily

The state of agent tools

What our own probes see across 92,977 listings (x402 APIs, MCP servers and A2A agents): how many answer, which protocol versions they speak, how ready they are for an agent to call, and what they charge.

As of 2026-11-11 06:00 UTC Methodology JSON CSV Cite

Indexed
7,334
Trend starts 2026-11-11
Listings in our index
Reachable
6,287
Trend starts 2026-11-11
85.7% of indexed · Answered the last probe
Protocol verified
2,199
Trend starts 2026-11-11
30.0% of indexed · Answers A2A JSON-RPC
Readiness A or B
989
Trend starts 2026-11-11
13.5% of indexed · Ready for an agent to call
01 · Funnel

85.7% of indexed A2A agents answer our probe, and 30.0% answer JSON-RPC.

Each step keeps only the listings that passed the one before. Indexed is everything any source lists; the last step is our readiness grade A or B.

A2A agents

  1. Indexed7,334
    100.0% of indexed
  2. Has an Agent Card URL7,239
    98.7% of indexed · 98.7% of previous
  3. Card fetched6,287
    85.7% of indexed · 86.8% of previous
  4. Answers JSON-RPC2,199
    30.0% of indexed · 35.0% of previous
  5. Readiness A or B989
    13.5% of indexed · 45.0% of previous
Measured 2026-11-11 06:00 UTC from the latest probe of every listing. Method JSON
02 · Sources

23.8% of A2A agents are listed by more than one source.

Which directories and registries list what we index, and how many of their listings answered our last probe. A listing found by several sources is counted once in the index.

A2A agents

SourceListingsReachable
agenstry5,26387.1%
own /.well-known crawl2,47791.2%
a2a-registry1,03591.9%
a2aregistry85683.6%
provider submissions15588.4%
chiark950.0%
awesome-a2a5090.0%
manual1172.7%
Listed by more than one source: 23.8%
Source membership as recorded by our crawlers; reachability from the latest probe. Method JSON
03 · Protocols

29.1% of reachable A2A agents declare 1.x; 1.3% carry a signature that verifies.

The protocol revision each reachable listing reports: the MCP version returned by initialize, the A2A version declared in the Agent Card, and the x402 version seen in the 402 challenge.

A2A protocol version

DeclaredShareCount%
1.x
1,829 29.1%
0.3
2,259 35.9%
0.2 and older
140 2.2%
Other
91 1.4%
Not declared
1,968 31.3%

Agent Card signatures: 84 verify, 225 present but do not verify, 5,978 unsigned.

Reachable listings only, as of 2026-11-11 06:00 UTC. Method JSON
04 · Readiness

13.5% of A2A agents grade A or B; 31.6% grade F.

Readiness grades whether an agent could call the listing today: protocol checks, declarations, uptime and freshness. It is shown on each listing and does not change search order, which uses the quality score.

ProtocolGrade mixABCDF
A2A agents 51
0.7%
938
12.8%
1,572
21.4%
2,455
33.5%
2,318
31.6%

Where reachable A2A agents lose points (average per agent)

Live JSON-RPC
−13.9
JWS signature
−9.8
Verified identity
−6.3
Protocol version
−5.2
Security declaration
−4.4
Skill declaration
−3.1
Freshness + modern flags
−2.1
Valid Agent Card
−0.6
Uptime (30 days)
0
Grades stored by the daily readiness job. Method JSON
05 · Reliability

Median response for A2A agents is 373 ms; p95 is 1125 ms.

30-day uptime counts only listings with at least five probes; probes a host refused (HTTP 429, or a 403 we were not let through) are left out. Latency is the last successful probe from our server.

A2A agents

Median latency
373 ms
p95 latency
1,125 ms

30-day uptime (0 tracked)

Probe history is still building; uptime appears once listings have five probes.

Probe history of the last 30 days, as of 2026-11-11 06:00 UTC. Method JSON
07 · Access

74.7% of reachable A2A agents declare no security scheme.

How a caller is expected to authenticate, as declared by the listing. MCP servers that accept x402 are counted as pay-per-call even when they also take a key.

A2A agents (Agent Card security)

Declared schemeShareCount%
mTLS
75 1.2%
OAuth2 + PKCE
120 1.9%
Other declared scheme
1,048 16.7%
Declared public
347 5.5%
Not declared
4,697 74.7%
Reachable listings, declarations only; we do not attempt to log in. Method JSON
09 · Topics

'payment' is 8.6% of reachable A2A agents but 1.7% of MCP servers.

Share of reachable listings whose name or description mentions each topic word. Darker cells mean a larger share; compare across a row to see where one protocol has supply and another has little.

TopicA2A agents
ai 33.3%
search 7.5%
data 13.5%
github 1.1%
code 3.3%
payment 8.6%
web 5.3%
email 2.7%
video 1.3%
llm 4.7%
crypto 3.9%
wallet 5.0%
image 1.1%
pdf 1.3%
analytics 1.1%
document 2.0%
security 2.6%
social 1.6%
news 1.3%
knowledge 2.2%

Largest gaps

  • payment: 8.6% of A2A agents, 1.7% of MCP servers
  • wallet: 5.1% of x402 APIs, 0.9% of MCP servers
Keyword match on name and description; one listing can count for several topics. Method JSON
10 · Growth

325 A2A agents were first seen in the last 7 days; 85 went down.

Listings by the day any source first showed them to us, over the last 90 days. Our crawlers started at different dates, so early spikes partly reflect when a source was added.

A2A agents

New in 7 days
325
Went down in 7 days
85
2026-08-14: 212026-08-15: 212026-08-16: 322026-08-17: 212026-08-18: 42026-08-19: 82026-08-20: 32026-08-21: 22026-08-22: 22026-08-23: 72026-08-24: 62026-08-25: 42026-08-26: 62026-08-27: 52026-08-28: 52026-08-29: 32026-08-30: 32026-08-31: 42026-09-01: 82026-09-02: 72026-09-03: 932026-09-04: 32026-09-05: 52026-09-06: 52026-09-07: 72026-09-08: 4832026-09-09: 822026-09-10: 172026-09-11: 192026-09-12: 422026-09-13: 282026-09-14: 122026-09-15: 172026-09-16: 12026-09-17: 632026-09-18: 212026-09-19: 252026-09-20: 292026-09-21: 122026-09-22: 192026-09-23: 7412026-09-24: 992026-09-25: 522026-09-26: 432026-09-27: 282026-09-28: 432026-09-29: 692026-09-30: 472026-10-01: 1122026-10-02: 1452026-10-03: 792026-10-04: 982026-10-05: 912026-10-06: 872026-10-07: 582026-10-08: 282026-10-09: 472026-10-10: 142026-10-11: 212026-10-12: 1452026-10-13: 692026-10-14: 352026-10-15: 572026-10-16: 322026-10-17: 522026-10-18: 642026-10-19: 632026-10-20: 672026-10-21: 712026-10-22: 3922026-10-23: 612026-10-24: 502026-10-25: 652026-10-26: 472026-10-27: 372026-10-28: 582026-10-29: 422026-10-30: 542026-10-31: 1372026-11-01: 802026-11-02: 352026-11-03: 492026-11-04: 572026-11-05: 1082026-11-06: 402026-11-07: 282026-11-08: 532026-11-09: 582026-11-10: 382026-11-11: 0
2026-08-142026-11-11
First-seen dates from listing sources. Method JSON
Scope & limits

Methodology

Every number is a count over the agent-tools.cloud index at the time shown above, recomputed once a day after our probes run. It is not a census of the whole ecosystem: listings no public source has shown us are missing, and private deployments are invisible to us.

Funnel. Reachable means the last probe got a valid answer. Verified means a valid 402 challenge for x402, a full MCP initialize plus tools/list, or an A2A JSON-RPC reply on the declared interface.

Sources. Duplicates across sources are merged by endpoint; each source a listing came from is kept.

Protocols. Versions are what the listing reports or declares; we do not infer them from behaviour. A2A signatures are verified against the key the card points to on its own site.

Readiness. Criteria and weights are on the About page. Points earned from live probes decay after 30 days without a fresh one.

Reliability. One probe per listing per day from one server; latency includes our network path and is not a provider SLA.

x402. Price per API is the lowest amount its payment terms ask for one call, in USD (USDC read at par). The x402 version is counted only where our resource probe recorded it. Settlement network falls back to the chains a listing declares when the challenge does not name one.

Access. Declared by the listing or its card; not tested with credentials.

Safety. Pattern rules over tool metadata only; no code is executed.

Topics. Whole-word match of a fixed word list on name and description. Listings whose text names more than five topics (gateway catalogues) are left out: 1,201 x402 APIs, 169 MCP servers, 55 A2A agents.

Growth. Earliest first-seen date across a listing's sources.

Reuse

Cite and download

Free to reuse under CC BY 4.0 with a link to this page. The full snapshot is at /stats.json; headline numbers for every day are at /stats/daily.csv.

agent-tools.cloud. "The state of agent tools." 2026-11-11. https://agent-tools.cloud/stats

@misc{agenttools_stats_20261111,
  author = {agent-tools.cloud},
  title  = {The state of agent tools},
  year   = {2026},
  note   = {Snapshot 2026-11-11 06:00 UTC},
  url    = {https://agent-tools.cloud/stats}
}