#1658·registry

Migrate ReMCP registry namespace after GitHub repository transfer

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

Summary

ReMCP moved its public repository from the personal GitHub namespace to the getremcp organization. The Official MCP Registry still has the old identity, which owns the same remote URL and blocks publication under the canonical organization namespace.

Existing registry entry

  • Server: io.github.antonbaider/remcp
  • Latest visible version: 0.2.79
  • Remote: https://remcp.site/mcp

Canonical identity now

  • Server: io.github.getremcp/remcp
  • Public repository: https://github.com/getremcp/remcp
  • Current release: 0.2.94
  • Remote: https://remcp.site/mcp

The repository has been transferred to the organization and current releases are published from getremcp/remcp. GitHub Actions OIDC publication for the new identity is ready, but the Registry correctly rejects/skips it because the old identity still owns the remote URL.

Request

Please migrate the existing Registry ownership/identity from io.github.antonbaider/remcp to io.github.getremcp/remcp, or delete/deprecate the old identity sufficiently to release the remote URL so the canonical organization identity can be published.

I am the owner/publisher of both the previous personal repository and the current getremcp organization repository.

Reproduction

Current Registry lookup for io.github.getremcp/[email protected] returns 404, while io.github.antonbaider/remcp@latest resolves and points at the same https://remcp.site/mcp remote.

Our release workflow intentionally fails closed for this migration state and does not try to duplicate the remote under a second identity.

Source: modelcontextprotocol/registry