MCP Server Security

MCP Registry v1.8.8: key listings by name and version

The official MCP Registry released v1.8.8 on 6 Nov 2026. Its notes say different server names may now share a remote URL, and that consumers should key listings by server name and version rather than assuming URL uniqueness. Teams that build approved-server lists from registry data should check their matching logic.

Facts read on .

The release notes are short and operational. They state that the release uses the source commit validated in staging and that no database migration is required. The one behavior note concerns identity: a remote URL can now appear under more than one server name.

An approved-server catalog that treats a remote URL as the identity of a server could map two listings to one entry, or approve a second name because its URL matches an approved one. Keying by name and version, as the notes advise, keeps a reviewed version distinct from a later one.

The registry's own about page calls it a preview that stores metadata pointing at packages hosted on npm, PyPI and Docker Hub, with namespace management through DNS verification. The registry holds pointers, not code, so a catalog still needs to review the package behind each entry.

Sources