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

[antonbaider]

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.

[antonbaider]

Additional proof from the current v0.2.80 release attempt:

• workflow: https://github.com/getremcp/remcp/actions/runs/35612574805
• server.json validation: ✅
• GitHub Actions OIDC login for getremcp/remcp: ✅
• publish response: HTTP 400 only because the historical entry still reserves the production remote:

remote URL https://remcp.site/mcp is already used by server io.github.antonbaider/remcp

So the namespace/OIDC migration itself is now confirmed working for io.github.getremcp/*; the remaining blocker is exclusively the old Registry record / remote-URL reservation.

The canonical public repository is now https://github.com/getremcp/remcp, and the old GitHub URL redirects there. v0.2.80 contains server.json with:

• name: io.github.getremcp/remcp
• repository: https://github.com/getremcp/remcp
• remote: https://remcp.site/mcp

An administrative rename preserving history would be ideal; otherwise deleting/releasing the old io.github.antonbaider/remcp reservation is fine. Thank you.

[antonbaider]

One more ownership/transfer proof that may make an administrative rename easier:

• GET /repos/getremcp/remcp → repository id 1373231892, node id R_kgDOUdnbFA, full name getremcp/remcp
• GET /repos/antonbaider/remcp → the same repository id 1373231892, the same node id, and current full name getremcp/remcp

So GitHub itself resolves the historical and canonical paths to the exact same repository object. The current Registry state is still io.github.antonbaider/remcp@0.2.79 on https://remcp.site/mcp; io.github.getremcp/remcp still returns 404 until the remote reservation is migrated.

[antonbaider]

Current Registry/API snapshot after the latest public release (v0.2.84):

• GET /v0/servers/io.github.getremcp%2Fremcp/versions/latest → 404 Server not found
• GET /v0/servers/io.github.getremcp%2Fremcp/versions/0.2.84 → 404 Server not found
• GET /v0/servers/io.github.antonbaider%2Fremcp/versions/latest → 200, still 0.2.79, status active, remote https://remcp.site/mcp
• public repository/release is now getremcp/remcp@v0.2.84, with server.json targeting io.github.getremcp/remcp

This confirms the remaining blocker is still only the legacy Registry identity / remote-URL reservation. No remote endpoint migration is required.