What is the official MCP Registry?

What an entry says

Each entry has a name in reverse-DNS form - io.github.<account>/<server> for a publisher verified through GitHub, or a domain the publisher has proved it controls, written in reverse. Then a short description, a version, and optionally a title, a website and a source repository.

Most important, it says how to reach the server: remotes, each a URL with its transport and any headers it needs; and packages, each naming a package registry (npm, PyPI, NuGet, an OCI image registry, an MCP Bundle download), the identifier, the version, the transport and the environment variables and arguments the program expects.

What it does not do

The registry holds metadata only: the code stays on npm, PyPI, Docker Hub, GitHub and the like. Its moderation policy removes illegal content, malware, spam and servers that do not work, but not low-quality or duplicate ones, and tells readers to assume minimal-to-no moderation. Downstream catalogues are expected to add their own curation.

Versions and status

Each publish adds a version, and published versions do not change; the latest is marked as such. An entry's status can be active, deprecated or deleted, and deleted entries are hidden from the default listing.

How this directory uses it

This directory reads the latest version of every entry, leaves out what is deprecated, test, placeholder, duplicate, boilerplate or unreachable, assigns a category by keyword from the server's own summary, and gives each remaining server a page with everything its entry states.