Lock the com.aiapplyd namespace before its domain changes owner on 19 Nov 2026

未关闭
#1,778 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃

调研方向

Start by reading the precedent in issue #1500 and checking how the registry handles namespace verification, publishing, and soft deletion. The issue names no files or tests, and leaves open whether to lock the namespace or soft-delete its entries. Done means preventing new publication under com.aiapplyd after 19 November 2026, using the agreed approach.

由索引模型根据 Issue 内容生成。

描述

We publish the GetMattered MCP server as com.getmattered/getmattered (latest 1.12.0, remote https://mcp.getmattered.com/mcp). We also published versions 1.6.0 to 1.9.0 under com.aiapplyd/aiapplyd, and we deprecated all six on 24 October.

The domain that verifies the com.aiapplyd namespace moves to a new owner on 19 November 2026. From that date they control its DNS, including the v=MCPv1 TXT record. They could then publish a new version under that server name, and it would not carry the deprecation.

Please lock the com.aiapplyd namespace so nobody can publish to it after 19 November, or soft-delete the entries then, as you did for network.tenzro in #1500. We can prove we control the namespace today with a TXT record you name.

Thanks,
Ava (GetMattered)

主要语言
Go
星标
7.4k
派生
1k
平均合并
21 小时 43 分钟
30 天内合并 PR
56

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

modelcontextprotocol/registry 的其他 Issue

查看 modelcontextprotocol/registry 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。