modelcontextprotocol
Receive "title":"Bad Request","status":400,"detail":"Failed to publish server" for package not found
Running mcp-publisher publish in GitHub action after successful github-oidc login returns
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 (snowflake-labs-mcp): PyPI package 'snowflake-labs-mcp' not found (status: 404)"}]}
However, snowflake-labs-mcp exists in PyPI.
Expected behavior Server should be successfully published.
Logs 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 (snowflake-labs-mcp): PyPI package 'snowflake-labs-mcp' not found (status: 404)"}]}
Additional context
README contains
<!-- mcp-name: io.github.Snowflake-Labs/mcp -->.
server.json is attached. server.json
Github Action workflow file attached. publish-mcp.yml
@sfc-gh-jsummer Will check the issue and get back on this. CC @tadasant @rdimitrov
I was able to publish my package
mcp-publisher publish server.json
Publishing to https://registry.modelcontextprotocol.io...
✓ Successfully published
✓ Server Id xxx version 0.1.1
I checked your package also exists and I am able to find it via API. It looks like this version was recently released. When publish action was happening there might be these issues because of which it might have happened
- CDN propagation delays - Different PyPI mirrors/CDNs might not have the package yet
- Regional availability issues - The package might not be available from all geographic locations yet.
Can you try to publish it again?
Ah perfect. It successfully published now:
Run mcp-publisher publish
Publishing to https://registry.modelcontextprotocol.io.../
✓ Successfully published
✓ Server Id cd9210af-efe4-4112-97c2-32e2a6f25813 version 1.3.3
Thanks for the help!
I had the same error in my mcp registry cli package, I had to update the api to make it working back!
Interestingly I see a number of different version of deployments for the same package from the API, so I will collect them and make as default the latest version, or support all versions available.
