Request: delete io.github.PersonAIzer/mcp (org renamed to PERSONAIZER, case mismatch blocks self-service)
维护者通常 6 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- go
- 领域
- authorization, backend
调研方向
Start from the reproduced failure: mcp-publisher status --status deleted --all-versions io.github.PersonAIzer/mcp returning 403. Locate where the registry compares the requested server name against the identity granted by mcp-publisher login github (the case-sensitive check that yields io.github.PERSONAIZER/* vs io.github.PersonAIzer/*) and where that permission decision is made. Done means versions 1.0.0 and 1.0.1 are marked deleted after org ownership of PERSONAIZER is verified, or the name comparison no longer blocks the legitimate owner; note this ultimately needs a maintainer with registry write access, not a drive-by patch.
由索引模型根据 Issue 内容生成。
描述
Please delete all versions of io.github.PersonAIzer/mcp (1.0.0 and 1.0.1).
Why: we discontinued this MCP server. The endpoint https://sessions.personaizer.com/mcp is being shut down and the listing repo github.com/PERSONAIZER/mcp has been deleted. Our REST API at https://www.personaizer.com/developers replaces it.
Why we can't do it ourselves: the server was published while our GitHub org was spelled PersonAIzer. The org is now PERSONAIZER, so mcp-publisher login github grants io.github.PERSONAIZER/*, and the case-sensitive name check rejects the status change:
mcp-publisher status --status deleted --all-versions io.github.PersonAIzer/mcp
Error: server returned status 403: {"title":"Forbidden","status":403,"detail":"You do not have publish or edit permissions for this server"}
I'm an owner of the PERSONAIZER org (the publisher of this entry). Happy to verify in any way you need. Thanks!
- 主要语言
- Go
- 星标
- 7.3k
- 派生
- 1k
- 平均合并
- 4 天 13 小时
- 30 天内合并 PR
- 15
环境准备
- 提供 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 ·
维护者通常 6 天内回复
-
难度 1/5 1 小时以内 新手友好度 80/100
modelcontextprotocol/registry#1657 ·
维护者通常 6 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
modelcontextprotocol/registry#1652 ·
维护者通常 6 天内回复
-
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 于 79 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/registry#1465 · 1 条评论 ·
维护者通常 6 天内回复
-
GitLab repository URLs with nested groups/subgroups are rejected by validator可能已有人在做 @anneheartrecord 于 118 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 84/100
modelcontextprotocol/registry#1359 ·
维护者通常 6 天内回复
查看 modelcontextprotocol/registry 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
enhancement pkg:sdk
难度 2/5 1-3 小时 新手友好度 80/100
aws/aws-durable-execution-sdk-go#144 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
cloudflare/cloudflared#1761 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复