Agent MCP Directory

The directory

1,336 companies, each checked for an MCP server, a CLI and an OpenAPI file. Browse by MCP status, by auth type, by category or by letter. 263 listed tools to a client with no credentials; 533 more answered with a sign-in challenge and are not counted.

By MCP status

StatusCompaniesWhat it means
Verified263The endpoint answered a handshake with no credentials and listed its tools.
Sign-in required533Sign-in required, tools not seen, not counted: the endpoint answered 401 and pointed at OAuth metadata, so something MCP-shaped is there, but the connector never signs in and saw no tool list.
Credential wall19The endpoint asked for credentials and published no OAuth metadata, so it cannot be told apart from any other protected API. Not counted as an MCP server.
No answer47A source lists an endpoint, but it did not answer an MCP handshake on the day. Not counted.
No tools listed2The endpoint completed the handshake and listed no tools. Not counted.
None found472No source read for this edition names an MCP endpoint for the company, so there was nothing to connect to.

By auth type

Auth typeEndpointsWhat it means
No authentication263The server listed its tools to a client that sent no credentials.
API key19The server answered 401 or 403 and asks for a key or bearer token with no OAuth metadata for an agent to follow.
OAuth with client registration517The server publishes OAuth metadata and a registration endpoint, so a client can register itself without a human filling in a form first.
OAuth without client registration16The server publishes OAuth metadata but no registration endpoint, so a client must be registered by hand or identified by a client ID metadata document.
Auth not determined2The connector could not tell what the endpoint wants, usually because it did not answer.

By category

A to Z

Starts with

106 endpoints found by subdomain guess, search and submit a company.