About

How this directory is checked

Every service listed here is checked against its own public files: its llms.txt, its MCP manifest, its published API description or its own announcement. Every remote MCP server is also connected to once, to see whether it answers the MCP handshake and which tools it lists. A listing records what was found, when, and where.

Live check of remote MCP servers

On 2026-10-05, 9,860 of 16,682 remote MCP servers answered the MCP handshake and listed 154,231 tools between them; 4,996 required sign-in (3,930 pointing to OAuth metadata), 52 older SSE endpoints opened their stream and 1,774 did not answer as MCP servers. 194 more were not requested: their registry URL holds a placeholder to fill in, or is not a public https address.

What is checked. For every remote endpoint in a server's registry entry, this directory sends one MCP initialize request (protocol version 2025-06-18) over Streamable HTTP. If the server answers, it sends the initialized notification, asks for tools/list (up to five pages) and records the server's name and version, the protocol version it answered with, the number of tools and up to 50 tool names; then it ends the session. Endpoints on the older SSE transport are only opened, waiting up to ten seconds for the event that names their message endpoint.

What is not checked. No tool is called, no resource or prompt is read and nothing is signed in to: an endpoint that answers HTTP 401 or 403 is recorded as requiring sign-in, noting whether it points to OAuth authorization metadata. The check says nothing about what the tools do, how well or how safely, and it is a snapshot: a server that answered may be down later, and one that failed may have been briefly unavailable.

How it asks. Requests identify themselves as AgentReadyDirectoryCheck/1.0 with a link to this page, carry no credentials or cookies, wait at most 15 seconds, are retried only once after a dropped connection, and go to one host at a time. URLs with placeholders, plain-HTTP URLs, localhost and private addresses are not requested.

What the tool names are used for. Besides being shown on each server's page, the tool names place a server in a category when its own name and summary match none: if at least three of its tool names name one subject - travel, food and delivery, real estate, health, maps and transport, finance, shopping or media - twice as many as name any other subject and at least a quarter of all its tools, the server is listed there, and its page says the category came from its tool names. Tool sets that 20 or more servers list alike (gateway and template tools) and generic words such as search, get and list are left out first. How categories are assigned.

Why checks failed. HTTP 4xx error: 786; could not connect: 491; HTTP 5xx error: 243; no answer within 15 seconds: 181; answered, but not as an MCP server: 41; rate limited (HTTP 429): 20; refused the handshake: 12.

Who published a server. The MCP Registry accepts names under io.github.<account> only from someone signed in to it with GitHub as that user, or for that organisation, and names under a reversed domain such as com.example only from someone who has proved control of example.com - by a DNS record, which also covers its subdomains, or by a file at /.well-known/mcp-registry-auth (registry documentation). Each server page says which way its namespace was verified. That shows who published the entry, not that the product it names endorses it.

Sources and licences

SourceUsed forLicence
Official MCP RegistryMCP servers: names, endpoints, packages and the publisher's own summaryPublished for aggregators; facts only, summaries rewritten
Each service's own documentationWhich AI integrations a service offers, linked to the page that says soFacts only; no text copied
Each remote MCP server's own endpointThe live check: whether the endpoint answered the MCP initialize handshake, the server name, version and protocol version, and the names and number of its tools (tools/list); nothing called or signed in toFacts only (status, names and counts), recorded with the date
MCP Registry documentation: authenticationWhat a registry namespace proves: GitHub sign-in for io.github.* names, DNS or HTTP proof of a domain for reversed-domain namesFacts only
Each service's own website/llms.txt, /.well-known/mcp.json, /.well-known/ai-plugin.json and /agents.json, requested and recorded with status and dateFacts only (status and presence of each file)

No paid listings

No service, hotel or place pays to be listed, described or ranked.

Editorial policy: how entries are chosen, what a listing means, how to ask for a correction or removal, and how fresh the data is.