Summary
I'm the original publisher of io.github.bibi-bambi/skanfirmy. That GitHub account was renamed from bibi-bambi to bartosz-kuc, so the bibi-bambi login no longer exists and the namespace entry is orphaned. I'm republishing the server as io.github.bartosz-kuc/skanfirmy (v1.1.0, now 9 tools), but the old entry blocks it. Same pattern as #1191 / #1422 / #1388 (orphan after a GitHub rename) and #1127 (remote-URL conflict blocking republish).
Request
Please set io.github.bibi-bambi/skanfirmy, all versions, to status deleted. That releases the reserved remote URL so I can publish under the correct namespace.
The entry
Server name: io.github.bibi-bambi/skanfirmy
Version: 1.0.0 (status: active)
Remote URL: https://skanfirmy.pl/mcp
Republishing as: io.github.bartosz-kuc/skanfirmy v1.1.0
Errors confirming the block
Publishing under the new namespace returns 400: remote URL https://skanfirmy.pl/mcp is already used by server io.github.bibi-bambi/skanfirmy.
A self-service delete of the old entry (while logged in as bartosz-kuc) returns 403: You do not have publish or edit permissions for this server, because the registry keys namespace authority on the GitHub login string and bibi-bambi is no longer my login.
Why direct action rather than the rename-back workaround (#1378
I'd prefer not to use the temporary rename-back: the bartosz-kuc account holds active production infrastructure (a write-scoped deploy key, ~15 live repositories, CI, and a just-published npm package), so renaming it even briefly would break live deploys and free the bartosz-kuc handle for anyone to claim mid-window.
Ownership verification
Happy to prove it however is easiest: I control skanfirmy.pl (I can add a DNS TXT record or serve a file at a path you specify) and I currently hold the renamed account bartosz-kuc. Just say what you need.
Thanks for maintaining the registry!
Summary
I'm the original publisher of
io.github.bibi-bambi/skanfirmy. That GitHub account was renamed frombibi-bambitobartosz-kuc, so thebibi-bambilogin no longer exists and the namespace entry is orphaned. I'm republishing the server asio.github.bartosz-kuc/skanfirmy(v1.1.0, now 9 tools), but the old entry blocks it. Same pattern as #1191 / #1422 / #1388 (orphan after a GitHub rename) and #1127 (remote-URL conflict blocking republish).Request
Please set
io.github.bibi-bambi/skanfirmy, all versions, to statusdeleted. That releases the reserved remote URL so I can publish under the correct namespace.The entry
Server name:
io.github.bibi-bambi/skanfirmyVersion: 1.0.0 (status: active)
Remote URL:
https://skanfirmy.pl/mcpRepublishing as:
io.github.bartosz-kuc/skanfirmyv1.1.0Errors confirming the block
Publishing under the new namespace returns
400: remote URL https://skanfirmy.pl/mcp is already used by server io.github.bibi-bambi/skanfirmy.A self-service delete of the old entry (while logged in as
bartosz-kuc) returns403: You do not have publish or edit permissions for this server, because the registry keys namespace authority on the GitHub login string andbibi-bambiis no longer my login.Why direct action rather than the rename-back workaround (#1378
I'd prefer not to use the temporary rename-back: the
bartosz-kucaccount holds active production infrastructure (a write-scoped deploy key, ~15 live repositories, CI, and a just-published npm package), so renaming it even briefly would break live deploys and free thebartosz-kuchandle for anyone to claim mid-window.Ownership verification
Happy to prove it however is easiest: I control
skanfirmy.pl(I can add a DNS TXT record or serve a file at a path you specify) and I currently hold the renamed accountbartosz-kuc. Just say what you need.Thanks for maintaining the registry!