Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

The MCP registry checks a package at publish. Here’s what drifts after that.

说明与用途

MCP 注册表仅在发布和编辑条目时进行包检查,导致链接和版本漂移。2026‑10‑04 统计显示 13.3% 的条目存在不可访问的仓库、已撤回的包或不可安装的版本。已提出功能请求,计划定期重新验证并记录状态,避免自动删除。

问题

Registry entries can drift after initial validation, leading to broken links, withdrawn packages, and outdated metadata.

结果

At least 13.3% of 38,977 MCP registry entries had issues such as 404 repositories, withdrawn packages, archived repos, or non‑installable versions.

工作流

  • 1. Open the registry entry’s repository.url and verify it loads.
  • 2. Check that the listed package version is still published and not deprecated or yanked.
  • 3. If the package has been renamed or moved, publish an updated entry pointing to the new location.

证据

The registry checks that version when the entry is published: it fetches it from npm or PyPI and confirms the package names the server.

来源

The package check runs again only when the publisher edits the entry. Nothing re-checks entries on a schedule.

来源

Registry snapshot 2026-10-04: 38,977 servers (the latest version of each name).

来源

At least 5,192 of 38,977 entries (13.3%) had at least one of these issues.

来源

I opened a feature request on the registry, modelcontextprotocol/registry#1715. It asks to re-run the existing checks on a schedule and record the result (for example lastVerifiedAt plus a status) instead of deleting anything.

来源

  • 记录日期: 2026-10-24T02:11:10.499Z