Support nested catalogs (application/ai-catalog+json entries), with depth cap and cycle tracking
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- typescript
- 领域
- api, documentation, security
调研方向
先从 SDK 参考实现开始，然后阅读 docs/discovery.md 和 docs/best-practices.md。追踪 consumer 如何解析 catalog，并更新它以支持嵌套的 application/ai-catalog+json 条目，同时遵循文档中规定的深度上限并跟踪已访问的 URL。当 discovery 和 best-practices 文档与实现一起描述嵌套 catalog、深度限制和循环处理时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
An AI Catalog entry can point at another catalog rather than at an artifact: per the specification's Composability goal, "a catalog entry can have a type of application/ai-catalog+json". Hosts can use this to organize by team, product line, or business unit rather than flattening everything into one document at the domain root.
We do not currently account for this. A consumer that fetches a catalog, filters for application/mcp-server-card+json, and stops will silently find nothing on any domain that organizes by nesting — including the shapes the spec itself uses as worked examples.
Resolving nested catalogs is not just "recurse." The spec attaches two requirements:
- Depth limit. "Clients processing nested catalogs SHOULD impose a maximum nesting depth to prevent circular references. A depth limit of 4 is RECOMMENDED. Implementations MAY support deeper nesting but SHOULD document their limit." (See also ADR-0001.)
- Cycle tracking. "Clients SHOULD track the set of catalog URLs visited during recursive resolution and reject any catalog URL that has already been fetched in the current traversal path." This lives in the spec's Security Considerations — unbounded traversal is a denial-of-service vector, not just a correctness bug.
Scope
- SDK reference implementations — recursive resolution with a documented depth cap and a visited-URL set.
docs/discovery.md— document nested entries in the client discovery flow, and add the depth/cycle requirements to Security Considerations alongside the existing denial-of-service guidance.docs/best-practices.md— currently describes a single flat catalog. Update once the above lands.
Relationship to #43
Same shape: both are places where the AI Catalog spec supports something broader than the flat, well-known-path-only model this extension documents and implements today. Worth deciding whether they land together, since both change what "resolve a catalog" means for a consumer.
Not urgent
A single flat catalog at the well-known path is the common case, and nothing is blocked on this. Filing so the gap is tracked rather than rediscovered.
- 主要语言
- TypeScript
- 星标
- 10
- 派生
- 4
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/ext-server-card 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
modelcontextprotocol/ext-server-card#51 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 5/5 一周以上 新手友好度 35/100
modelcontextprotocol/ext-server-card#53 · 2 条评论 ·
-
难度 3/5 1-2 天 新手友好度 58/100
-
难度 3/5 1-2 天 新手友好度 55/100
查看 modelcontextprotocol/ext-server-card 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
jessepollak/home#2223 ·
维护者通常 1 天内回复
-
grep fixture corpus test follows the corpus's loop symlink under the receipt runner (fails on main)未关闭
难度 2/5 1-3 小时 新手友好度 68/100
code-yeongyu/senpi#3756 ·
维护者通常 1 天内回复
-
org:external package:deepagents priority:triage topic:memory topic:middleware type:bug
难度 2/5 1-3 小时 新手友好度 65/100
langchain-ai/deepagents#7059 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
osmlab/name-suggestion-index#12992 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
hemilabs/ui-monorepo#2506 ·
维护者通常 1 天内回复