MCP registry
The official index of MCP servers, where a publisher declares a server under a verified namespace so clients and directories can discover it.
What makes it wrong.
The mechanism, not the warning.
The registry verifies the published package, not the repository. A manifest can be correct while the package on the package manager carries no matching ownership marker, and publication fails for a reason that names neither file.
In detail.
A server is published with a manifest declaring its name, its package and its environment variables. Ownership of the namespace is proved either through a code host account or through a DNS record on the publisher's own domain, which is what a reverse-DNS name such as com.example is asserting.
Several third-party directories read from the registry, so an entry there tends to propagate without further submissions.