Request: delete io.github.Norcalnappy/atlasofplantbased-pct (1 version), orphaned after GitHub rename Norcalnappy -> AtlasDigitalDesign, holding the remote URL
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The orphaned record is stored in the registry backend; an admin must delete it via the management API or database. Confirm the repo 301 redirect and server.json on main as evidence. Done means io.github.Norcalnappy/atlasofplantbased-pct is removed and the remote URL is released for the new namespace.
由索引模型根据 Issue 内容生成。
描述
Hi,
My GitHub account was renamed from Norcalnappy to AtlasDigitalDesign on October 23, 2026. The one server I had published, io.github.Norcalnappy/atlasofplantbased-pct (version 1.0.0, published October 14), is now orphaned: GitHub OIDC resolves to io.github.AtlasDigitalDesign, so no credential I hold can deprecate or update the old record.
Republishing under the new namespace with the same remote failed on the remote URL rule:
Publishing io.github.AtlasDigitalDesign/[email protected] 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://atlasofplantbased.com/mcp is already used by server io.github.Norcalnappy/atlasofplantbased-pct"}]}
As a bridge, io.github.AtlasDigitalDesign/[email protected] is now published against https://atlasofplantbased.com/mcp/ (trailing slash; the same Pages Function answers there). I would like to move it back to the canonical https://atlasofplantbased.com/mcp once the old record is gone, and stop the orphaned record from being served as latest.
Ask: please mark all versions of io.github.Norcalnappy/atlasofplantbased-pct as deleted so the remote URL reservation is released. There is only the one version.
Evidence the two are the same publisher and server:
- The repository field on the old record, https://github.com/Norcalnappy/atlasofplantbased-mcp, 301-redirects to https://github.com/AtlasDigitalDesign/atlasofplantbased-mcp.
- The repo's
server.jsononmaincarries the new name and was published by the samepublish-mcp.ymlworkflow that published the original (run #1 on October 13, run #3 today). - The remote is a Cloudflare Pages Function on a domain I control, with the server card at https://atlasofplantbased.com/.well-known/mcp/server-card.json. Happy to add a DNS TXT record or anything else that helps.
Same situation as #1662, #1682 and #1688. Thanks for your time.
- 主要语言
- Go
- 星标
- 7.4k
- 派生
- 1k
- 平均合并
- 1 天 19 小时
- 30 天内合并 PR
- 22
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/registry 的其他 Issue
-
3 registry records that cannot resolve for any client, and a caution about single-pass dead counts未关闭
难度 2/5 1-3 小时 新手友好度 68/100
modelcontextprotocol/registry#1692 ·
维护者通常 1 天内回复
-
IsValidRemoteURL only blocks literal localhost/127.0.0.1 — misses [::1], 127.0.0.0/8, 0.0.0.0, and private/link-local addresses可能已有人在做 @amitvijapur 于 96 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/registry#1465 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 56/100
modelcontextprotocol/registry#1719 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 28/100
modelcontextprotocol/registry#1715 · 14 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 8/100
modelcontextprotocol/registry#1708 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/registry 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 73/100
prime-radiant-inc/evener#5028 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
-
[BUG] v4.2.9 PostgreSQL 启动迁移失败：DROP INDEX CURRENT_SCHEMA() 语法错误可能已有人在做 @renovate 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
OpenListTeam/OpenList#3267 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
openpubkey/opkssh#670 ·
维护者通常 1 天内回复