Methodology
Agents Index is meant to be a source you can cite. That only works if every number on a page can be traced to something we observed. This page says exactly what we observe.
Where listings come from
We read the official MCP Registry every day and keep the latest active version of each server. The registry checks that a publisher controls the domain or GitHub account in the server's name before it accepts a listing, so every publisher shown here has passed that check. Deprecated or deleted entries drop out on the next refresh.
We list servers that answered our probe, plus local packages with public source code. To keep the index useful, we show at most 20 servers per publisher, choosing their highest-scoring ones.
How we check status
For each remote endpoint our probe sends the standard MCP initialize request and then tools/list. It never calls a tool. Results:
- Online: the endpoint completed the handshake and listed its tools.
- Online · sign-in required: the endpoint answered but asked for OAuth or an API key. That is normal for agents that act on your account.
- Unreachable: no valid MCP answer within 12 seconds.
- Runs locally: the server ships as an npm, PyPI or Docker package and has no public endpoint to check.
Uptime is the share of our recent daily checks (up to 14) that came back online or sign-in required. Response time is how long the initialize call took from our probe.
Evidence score
Out of 100: live status (up to 40), number of tools it exposes (up to 20; endpoints that require sign-in get a neutral 10 because they hide tools from anonymous checks), first-party endpoint hosted on the publisher's own verified domain (8), how widely used the publisher's verified domain is on the Tranco top-1M list (top 10k: 20, top 100k: 14, top 1M: 6), uptime (up to 10), linked source code (8), website (6), domain-verified publisher (6; GitHub-verified 3), freshness of the last registry update (up to 10), and a usable description (4). Category rankings sort by this score.
Neutrality
Rankings cannot be bought. We sell two things, both described on the advertise page: a fast-track review of a submission (it only makes us look sooner; the listing still has to pass the same checks), and sponsored slots, which sit above the ranking with a Sponsored label and a rel="sponsored" link. Neither changes an evidence score or a rank.
Badges
- Official: the endpoint is on the publisher's own registry-verified domain, and that domain is not a shared hosting platform.
- Popular: the source repository has 500 or more GitHub stars, or the publisher's domain is in the Tranco top 10,000.
- New: first appeared in the official MCP Registry in the last 30 days (from the registry's version history).
- Partner: the publisher claimed the listing and links to it, for example with our README badge.
- Sponsored: paid placement. Always labeled.
Categories
Categories are assigned automatically from the description, name and tool names. Publishers can correct them by claiming their listing.