Publisher withdrawal request: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/herald (internal infrastructure, not a public server)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
This is a takedown request for one registry entry, not a code change, and the payload names no files or tests. Confirm with a maintainer who has registry removal rights and check the project's withdrawal policy before touching any data. Done means the listing and all its versions are removed and downstream syncs stop showing it.
由索引模型根据 Issue 内容生成。
描述
Publisher withdrawal request
We are the publisher of the MCP Registry namespace io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC (GitHub account cetech-ai, organization CYAN-ECLIPSE-TECHNOLOGIES-LLC) and request withdrawal/removal of the following server entry, all versions:
- Server:
io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/herald(Cyan Eclipse Herald MCP) - Repository: https://github.com/CYAN-ECLIPSE-TECHNOLOGIES-LLC/eclipse-herald-mcp
Reason: Herald is internal identity infrastructure (credential issuance and mandate signing) for our firm. It was published to the registry during an early fleet-wide distribution pass; it is not a product we offer, its repository is private, and there is no supported public installation path. Leaving the entry public misrepresents an internal component as a downloadable community server. We are withdrawing it as publisher, following the precedent of our earlier withdrawal request (#1759).
Please remove the entry from the registry so downstream directories that sync from the registry (e.g. Glama) drop the listing as well. Thank you.
- 主要语言
- Go
- 星标
- 7.4k
- 派生
- 1k
- 平均合并
- 13 小时 43 分钟
- 30 天内合并 PR
- 51
环境准备
- 提供 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 于 104 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/registry#1465 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1 小时以内 新手友好度 8/100
modelcontextprotocol/registry#1785 ·
维护者通常 1 天内回复
-
难度 2/5 1 小时以内 新手友好度 35/100
modelcontextprotocol/registry#1784 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 12/100
modelcontextprotocol/registry#1783 · 7 条评论 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/registry 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
router-for-me/CLIProxyAPI#7209 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
Azure/azure-storage-azcopy#3674 ·
维护者通常 1 天内回复
-
date_time, url_encode, html_escape, to_unix_time, contains_all and contains_any panic when called without arguments可能已有人在做 @antcybersec 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
projectdiscovery/dsl#372 ·
维护者通常 1 天内回复
-
blocked-needs-validation
难度 2/5 1-3 小时 新手友好度 62/100
projectcapsule/capsule#2265 ·
维护者通常 1 天内回复
-
Remove "Model catalog refresh unavailable" warning from OpenRouter agent runs可能已有人在做 @superplanehq-integration 今天认领。 未关闭superplane
难度 2/5 1-3 小时 新手友好度 75/100
superplanehq/superplane#9164 ·
维护者通常 1 天内回复