Directory
The services AI assistants can actually use.
163 services that an AI assistant can call directly - through an MCP server, an app inside ChatGPT or Claude, a published API or an llms.txt - each checked against the service's own public files.
The landscape in numbers
What was found when this directory was compiled, 2026-10-04.
- Servers in the MCP Registry
- 37,928
- Sites checked
- 1,504
- With a real llms.txt
- 952
- With an MCP manifest
- 242
MCP Registry servers by category
| other | 13,634 | |
|---|---|---|
| developer | 6,202 | |
| data | 6,169 | |
| finance | 3,823 | |
| productivity | 3,156 | |
| media | 2,249 | |
| maps & transport | 702 | |
| shopping | 488 | |
| travel | 479 | |
| health | 437 | |
| real estate | 330 | |
| food & delivery | 259 |
Categories assigned by keyword from each server's own name and summary (a few from the tool names it listed in the live check); deprecated, empty and test entries excluded.
What the sites answered
| File | HTTP 200 | Real file |
|---|---|---|
/llms.txt | 1,015 | 952 |
/.well-known/mcp.json | 335 | 242 |
/.well-known/ai-plugin.json | 176 | 75 |
/agents.json | 147 | 24 |
Of 1,504 sites. A 200 that returned an HTML page or an error document is not counted as a real file.
Every MCP Registry server, a page each
28,535 servers from the official MCP Registry, each with its endpoint, packages, version, dates and how to connect.
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. The check connects and lists tools only; it doesn't run tools, sign in or test security. How the live check works
Recently updated
| Server | Runs | Updated |
|---|---|---|
| ALEX Evidence VerifyVerify signed ALEX Evidence Packages. Fails closed on signature or schema errors. | Local · stdio | 2026-10-04 |
| Art Spotter - Eye of the BeholderOriginal art and prints from independent artists, fair prices, and help for artists to sell. | Remote · HTTPLive check: ✓ handshake | 2026-10-04 |
| Beesknees MCPThe Bee's Knees - a monetized multiplayer race to the queen, on Tollbooth DPYC. | Remote · HTTPLive check: ✓ handshake | 2026-10-04 |
| CardVolumeVerified trading card sales and prices by grade: Pokemon, Magic, Yu-Gi-Oh., sports, Harry Potter. | Remote · HTTPLive check: ✓ handshake | 2026-10-04 |
| CliCross-tool decision memory for AI coding agents: search your decision graph, check changes over MCP. | Local · stdio | 2026-10-04 |
| CloudovňaOrder, configure and deploy Docker containers and PostgreSQL or SQL Server databases in the EU. | Remote · HTTPLive check: sign-in required | 2026-10-04 |
| corralctlSearch code and symbols across every clone in your corralctl workspace. Zero network calls. | Local · stdio | 2026-10-04 |
| Curagent Title RiskAI title risk analysis for US real estate closing docs. Get an API key at curagent.io. | Remote · HTTPLive check: ✓ handshake | 2026-10-04 |
By access type
MCP server
A Model Context Protocol server: a standard interface that AI assistants such as Claude, ChatGPT and others can connect to, to call the service's tools directly.
ChatGPT app
An app inside ChatGPT: the assistant can call the service while you chat, after you connect it.
Claude connector
A connector in Claude: the assistant can read from or act in the service once you connect it.
OpenAPI description
A published machine-readable API description that an agent can read to learn how to call the service.
llms.txt
A plain-text guide at /llms.txt that tells AI systems what the site is and where its key pages are.
Public API
A documented public API an agent can call, usually with a key from the service.
MCP servers by product
Categories
Learn
What is an MCP server?
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to outside tools and data. A service that runs an MCP serv…
What is llms.txt?
llms.txt is a plain-text file at the root of a website - /llms.txt - that tells AI systems what the site is and lists its most useful pages …
How AI assistants find and book travel
An assistant answering a travel question has three ways to get facts: from what it learned in training (often out of date), from searching t…
How listings are verified
For every service, the directory requests the public files that declare an AI integration - /llms.txt, MCP manifests, OpenAPI descriptions -…
MCP transports: stdio, Streamable HTTP and SSE
Every MCP connection carries the same messages - JSON-RPC 2.0 requests, responses and notifications - but they can travel in different ways.…
Remote or local: which kind of MCP server to use
An MCP server is either remote - run by its publisher and reached at a URL - or local - a program on your own computer that the assistant's …
How to add an MCP server to an AI assistant
The steps differ from one assistant to the next, and change often, but they follow two patterns: give the assistant a URL, for a remote serv…
What is the official MCP Registry?
The official MCP Registry, at registry.modelcontextprotocol.io, is a public catalogue of MCP servers run by the Model Context Protocol proje…
What goes in an llms.txt file
llms.txt is a proposal, published at llmstxt.org in September 2024, for a Markdown file at a site's root that gives language models a short,…
OpenAPI for AI agents
An OpenAPI document describes an HTTP API in a machine-readable form: its endpoints, the parameters each takes, the shape of each response a…
How AI assistants find travel availability
Whether a room, a seat or a table is free, and at what price, changes by the minute and depends on the dates, the number of people and the o…
Before you connect an MCP server: a checklist
Connecting an MCP server lets an assistant act with whatever access that server has. A few checks before connecting are worth the minute the…