MCP Registry
The MCP Registry is the official, centralized metadata directory at registry.modelcontextprotocol.io for publicly accessible MCP servers, verifying who published each one through namespace authentication rather than scanning what the server's code actually does. AdminKit's guide to securing an MCP server covers why a server's listing there is not, by itself, a safety signal worth trusting.
By AdminKit team, Netbase JSC · Updated
The MCP Registry is the official, community-run metadata directory for publicly accessible MCP servers, publishing a standardized server.json record (name, install location, declared capabilities) for each one so MCP clients and downstream marketplaces can discover them. Its own documentation is explicit about what that listing does and doesn’t mean: namespace authentication ties a server’s reverse-DNS-style name to a verified GitHub account or domain, proving who published it, while actual security scanning is delegated entirely to the underlying package registry (npm, PyPI, Docker Hub) or to downstream aggregators that choose to add it. The registry’s own moderation policy says so directly: it removes malware, spam and illegal content, but explicitly does not remove a server just for having security vulnerabilities or being low quality. That gap is exactly what makes tool poisoning effective against a server pulled from the registry without further review — authenticity and safety are two different guarantees, and the registry only makes the first one.