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