Standards measurements

Each week APIs.io probes the website of every provider in the catalog for the well-known documents that agent and commerce standards define, and publishes what it finds. The counts always carry their denominators, and every week's file is kept, so the series can be compared over time. The data is free to use under CC BY-NC-SA 4.0.

Latest: 2026-11-02

Providers with a website31534
Distinct hosts probed28785
Hosts reachable27280
Hosts answering 200 on a nonsense path2578
Serving /.well-known/ucp672
Serving /.well-known/ucp.json425
Serving /.well-known/agent-card.json418
Serving /.well-known/api-catalog853
Serving /.well-known/agent-descriptions3
Serving /.well-known/ai-catalog.json410
Serving /apis.json156
Serving /.well-known/http-message-signatures-directory94
Serving /llms.txt7872
Serving /.well-known/oauth-authorization-server2033
Serving /.well-known/openid-configuration703
Serving /.well-known/robots-content-signals1748
Serving /.well-known/security.txt2579

Download: latest JSON · latest CSV

Every week

Company MCP servers and the official registry (2026-11-01)

Of the verified providers on APIs.io with a hosted MCP endpoint, how many have that endpoint in the official MCP registry? This is an upper bound on what is missing, and totals only: no list of companies is published until each endpoint has been checked.

Verified providers with a hosted MCP endpoint1662
Matching a registry remote (URL 293, host 25, domain 18)336
Matching no registry remote1326 (80%)
Of those tested (1308): completed an MCP handshake with no credentials, so confirmed servers187
Answered 401, which fits an OAuth-protected server but does not prove one997
Did not answer as MCP (404, 403, not MCP, unreachable): likely our error, or gone124
Active registry servers with a remote, at the time35722

Method

Generated by scripts/probe_standard_wellknown.py and scripts/build_standard_evidence.py. Each standard's page shows the providers measured for it, for example UCP and A2A.