#1655·registry

Release ReMCP remote URL after repo transfer: io.github.antonbaider/remcp → io.github.getremcp/remcp

Author: antonbaiderCreated Sep 21, 2026Updated Sep 21, 2026

Summary

The ReMCP public repository was transferred from the personal account to the new GitHub organization:

  • old repository: https://github.com/antonbaider/remcp
  • canonical repository: https://github.com/getremcp/remcp
  • old Registry name: io.github.antonbaider/remcp
  • new Registry name: io.github.getremcp/remcp
  • production remote: https://remcp.site/mcp

GitHub redirects the old repository URL to the new organization repository.

What works

The current server.json validates successfully, and GitHub Actions OIDC authentication succeeds from getremcp/remcp. I am an owner of the getremcp organization.

What blocks the migration

Publishing the canonical namespace fails because the production remote remains reserved by the historical Registry entry:

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":"remote URL https://remcp.site/mcp is already used by server io.github.antonbaider/remcp"}]}

The failing GitHub Actions run is: https://github.com/getremcp/remcp/actions/runs/35611424706

Request

Could you please migrate/delete the historical io.github.antonbaider/remcp record, or otherwise release its remote-URL reservation, so the same production remote can be published under io.github.getremcp/remcp?

I would prefer preserving the historical version data if the Registry supports an administrative rename/migration; otherwise deleting the old record to free the URL is fine.

I can provide any additional ownership verification needed.

Source: modelcontextprotocol/registry