Labsco
MCP SERVER

Search a public directory of remote MCP endpoints — everything submitted, or only the ones verified to still answer.

MCP Plumbing: Proxies, Registries & Inspectors
Summary
An agent can find other MCP servers at runtime instead of at config time.

One call searches a directory of remote endpoints, and the live variants drop the ones that have stopped answering — so what comes back is a shortlist worth trying rather than a list worth checking.

What it is

An open directory of remote MCP servers that is itself a remote MCP server, at https://mcpub.dev/mcp. Anyone can submit an endpoint, there is no review step, and a crawler re-checks them so the live calls return only the ones that answered.

What you get
  • Keyword search across archived endpoints, paginated by offset and limit
  • The same search restricted to endpoints verified as still alive
  • The whole archive listed, or only the live subset
  • A single endpoint looked up by its URL
  • Your own endpoint submitted with a description
Requirements

A client that can reach a remote endpoint over HTTP. No account, no key, no review. To be listed, a domain needs a /.well-known/mcp.json — any content will do, even an empty object.