Our small MCP server was ready to list in the official MCP registry, except for one thing: its server.json pointed at an npm package, and the repo had no npm token, so the publish step could not run. The registry accepts other package types. One of them, MCPB, needs nothing but a GitHub release. Today the server is listed that way, and npm can be added later.
What the registry accepts
The registry stores metadata, not code. [src: https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/about.mdx ] Each entry in server.json points at a package somewhere else, and the registry docs list npm, PyPI, NuGet, Docker/OCI, MCPB and Cargo. [src: https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/package-types.mdx ]
For MCPB the rules are short: the file must be on a GitHub or GitLab release, its URL must contain the string mcp , and server.json must carry the file's SHA-256 as fileSha256 .…