registry

Why we included this project

If you're building an agent on the Model Context Protocol, the registry is the fastest way to see what MCP servers actually exist before you wire up your own integrations. It works like an app store for MCP servers. Creators publish standardized metadata covering the server's name, where to install it, how to run it, and what capabilities it offers, and clients or downstream marketplaces query a REST API to discover that metadata. That gives it two practical uses: a live API your host application or aggregator can call, and a reference for how server discovery and namespace authentication work across the ecosystem. Teams evaluating MCP for their stack can survey available servers, compare standardized install and config instructions, and learn what metadata a well-formed MCP server should expose.