How listings are verified

For every service, the directory requests the public files that declare an AI integration - /llms.txt, MCP manifests, OpenAPI descriptions - and records the HTTP status and the date.

Integrations announced on the service's own pages are linked to that page. Nothing is listed on the strength of a third party's claim.

A listing shows only what was found; a missing check is shown as not checked, never as a pass.

MCP Registry servers are shown as the registry states them - endpoint, packages, version, dates - after a quality bar that leaves out deprecated, test, placeholder, duplicate and boilerplate entries. A server page records what the registry says.

Remote servers also get a live check: each endpoint is sent the MCP handshake and asked for its list of tools, and the page shows what it answered and when. No tool is run and nothing is signed in to, so the check shows that a server answers, not that it works well or safely.

The bar for a server page · How we verify · The live check · Browse the directory →

More: What is an MCP server? · What is llms.txt? · How AI assistants find and book travel · MCP transports: stdio, Streamable HTTP and SSE · Remote or local: which kind of MCP server to use · How to add an MCP server to an AI assistant · What is the official MCP Registry? · What goes in an llms.txt file · OpenAPI for AI agents · How AI assistants find travel availability · Before you connect an MCP server: a checklist