Editorial policy

Services with a page of their own (163). Candidates come from an editorial list of well-known services. An integration — an MCP server, a ChatGPT app, a Claude connector, a public API for agents, an OpenAPI description — is recorded only when the service's own page or its official repository states it; the page is linked from the listing. Each service's site root is also requested for an llms.txt, an MCP manifest, a plugin manifest and an agents.json, and the result is recorded with its date. Nothing is listed on the strength of a third party's claim, and robots.txt is respected.

MCP Registry servers whose site answered (647). Servers in the official MCP Registry in the travel, maps and transport, food and delivery, and real-estate categories whose own website answered with a real llms.txt or manifest — a text file or a JSON object, not an error page dressed as one. One row per site, on the category page.

Server pages (28,535 of 39,052). Every entry in the official MCP Registry that clears a published bar has a page stating what the registry says about it. 10,517 entries were left out: deprecated or deleted, test and placeholder entries, entries with no stable endpoint or package, no stated repository or website, a summary that only repeats the name or is boilerplate shared by many entries, and duplicates of the same endpoint. The bar, with the count for each reason.

Publisher pages (1,728). Servers grouped by the namespace of their registry name, for every namespace with 2 or more servers. Publishers.

Categories. Assigned by the same keyword rules for every entry, from its own name and summary — never by hand, and never on request. A few entries sit in a category for a word they share with it.

Order. Lists are alphabetical, by number of servers, or by registry update date, as each list says. Nothing is ordered by payment, partnership or the operator's preference.

A listing means that the service's own pages or files, or its MCP Registry entry, stated what the listing shows, on the date shown. A file marked as answering was requested and returned a real file at that date.

It does not mean that the server or service was tested, reviewed for security or privacy, or that it works as described. It is not an endorsement, a recommendation or a ranking of quality, and it does not mean the service has any relationship with this directory. A registry name shows who published an entry — a GitHub account or the controller of a domain — not that it is the official server of the product it works with. Names and trademarks belong to their owners.

Before giving a server access to your accounts or files, check its publisher, repository and terms: a checklist.

No one can pay to be listed, to be placed higher, to be described differently, or to have a competitor removed, and no listing is sponsored. Links go where the service's own pages or its registry entry point — some publishers add their own tracking parameters to the addresses they state — and this directory adds no affiliate or tracking parameters of its own and earns nothing from a click. The directory's operator, Nexa AI, does not list its own services here.

Anyone can ask for a correction: the service itself, a server's publisher, or a reader who spots an error. Send the address of the page here, what is wrong, and a link to the service's own page, file or registry entry that shows the correct fact — a correction is made when the source confirms it, in the next data update.

A service can ask for its own listing page to be removed. A server page shows the MCP Registry entry as published, so the quickest way to change it is for the publisher to publish a new version, or mark the entry deprecated, in the registry: the page follows when the registry is next read. A publisher can also ask for a server page to be removed.

Requests go to the directory's operator, through its site: www.nexadirect.ai.

Agent-Ready is operated by Nexa AI.