Request: Delete server io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-benchkit-mcp (publisher withdrawal)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Read the registry FAQ and locate the server status update path and its tests; the issue does not name specific files. Confirm how a publisher withdrawal should be verified, then check whether the server can be set to "deleted" through an existing path. Done means the registry no longer offers this server while its API metadata remains accessible.
由索引模型根据 Issue 内容生成。
描述
Deletion Request
Server name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-benchkit-mcp
Version: 0.1.1
Published: 2026-10-27
We are the publisher of this server (GitHub org CYAN-ECLIPSE-TECHNOLOGIES-LLC; this issue is filed from the org's account). We have withdrawn this product — Eclipse Benchkit was a free vendor self-bench SDK, and we have retired it and removed it from our catalog and all of our own surfaces. The registry entry is now the only public listing that still offers it, and its description ("Free vendor self-bench SDK") advertises a product we no longer provide.
We attempted to remove it ourselves and found, per the registry FAQ, that publishers currently cannot delete or unpublish their own servers. Could you please set this server's status to "deleted" (or advise the correct publisher path if one now exists)?
We understand metadata remains accessible via the API after a status change — that is fine. We are the namespace owner and can verify control of the org/repository (https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-benchkit-mcp) however you require.
Thank you.
- 主要语言
- Go
- 星标
- 7.4k
- 派生
- 1k
- 平均合并
- 20 小时 25 分钟
- 30 天内合并 PR
- 39
环境准备
- 提供 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 于 100 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/registry#1465 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 49/100
modelcontextprotocol/registry#1758 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 3/100
modelcontextprotocol/registry#1755 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 48/100
modelcontextprotocol/registry#1749 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/registry 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
cloudevents/sdk-go#1346 ·
-
needs-triage
难度 2/5 1-3 小时 新手友好度 82/100
kubernetes/cloud-provider-aws#1517 · 1 条评论 ·
维护者通常 1 天内回复
-
agent-butler-finding chore
难度 1/5 1 小时以内 新手友好度 88/100
jordansmall/spindrift#6221 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 3 天内回复