Publishing fails with `registry validation failed for package 0`

[habedi]

Describe the bug

I want to publish this project to the MCP registry, but I get an error saying that the mcp-name is not included or available in the package README on PyPI.

I'm not sure, but I think this error is a bug and shouldn't happen with my settings.

To Reproduce
Steps to reproduce the behavior:

1. Follow the instructions in here.

Expected behavior

Publish should succeed.

Logs

mcp-publisher publish
Publishing to https://registry.modelcontextprotocol.io...
Error: publish failed: server returned status 400: {"title":"Bad Request","status":400,"detail":"Failed to publish server","errors":[{"message":"registry validation failed for package 0 (omni-lpr): PyPI package 'omni-lpr' ownership validation failed. The server name 'io.github.habedi/omni-lpr' must appear as 'mcp-name: io.github.habedi/omni-lpr' in the package README"}]}

Additional context

The mcp-name is set in the project's pyproject.toml (as a keyword) and is available on the package README on PyPI.

[Avish34]

Can you share your server.json? I can have a quick look.

[habedi]

Can you share your server.json? I can have a quick look.

It's here: https://github.com/habedi/omni-lpr/blob/main/docs/github_mcp_registry/server.json

[Avish34]

Thanks. Let me check.

[Avish34]

Hey @habedi ,
The way we validate is "mcp-name: {server_name}", but in your readme I can see it as mcp-name:io.github.habedi/omni-lpr. It basically violates the convention we use. There should be a space after colon. You can try again after adding the space.
cc: @domdomegg

[domdomegg]

From a registry feature perspective, possibly we should allow it with/without the space to be more forgiving here? I don't mind too much either way.

[habedi]

Hey @habedi , The way we validate is "mcp-name: {server_name}", but in your readme I can see it as mcp-name:io.github.habedi/omni-lpr. It basically violates the convention we use. There should be a space after colon. You can try again after adding the space. cc: @domdomegg

OK. Thanks.

I used mcp-name:io.github.habedi/omni-lpr based on the example I saw here. I think the example is inconsistent at the moment.

[Avish34]

@domdomegg can we also change the example?

[domdomegg]

Fixed, thanks! Removed from the keywords.

[habedi]

Hey @habedi , The way we validate is "mcp-name: {server_name}", but in your readme I can see it as mcp-name:io.github.habedi/omni-lpr. It basically violates the convention we use. There should be a space after colon. You can try again after adding the space. cc: @domdomegg

I changed the mcp-name:io.github.habedi/omni-lpr to mcp-name: io.github.habedi/omni-lpr in the keyword list of the package and published it to PyPI.

I still see the error:

mcp-publisher publish
Publishing to https://registry.modelcontextprotocol.io...
Error: publish failed: server returned status 400: {"title":"Bad Request","status":400,"detail":"Failed to publish server","errors":[{"message":"registry validation failed for package 0 (omni-lpr): PyPI package 'omni-lpr' ownership validation failed. The server name 'io.github.habedi/omni-lpr' must appear as 'mcp-name: io.github.habedi/omni-lpr' in the package README"}]}

How can I include the mcp-name: io.github.habedi/omni-lpr on the package README? Should it be done manually? Is there a more robust way?

[pree-dew]

@habedi you can try adding something like this in your Readme, it won't be visible and will solve the problem.

<!-- mcp-name: io.github.pree-dew/mcp-bookmark -->