If you are building on the official Model Context Protocol (MCP) registry, your dependency list is effectively a moving target. New data from ProtocolProbe, a directory that snapshots the registry daily, shows that between October 23 and October 31, 2026, the registry absorbed 5,161 new servers and 12,973 new versions. This represents a 10.5% increase in total entries in just eight days, proving that treating the registry as a static package manager is a mistake waiting to happen.

The Scale of Volatility

The sheer volume of change is staggering for a system meant to standardize AI agent interactions. The total registry size jumped from 48,551 entries to 53,637, while the historical version table grew by 28,423 rows. Of the 5,161 new servers, 43.6% were published under GitHub accounts (io.github.*), indicating a heavy reliance on individual developer repositories rather than centralized corporate entities. Furthermore, 839 of these new servers released a newer version before the window even closed, suggesting that initial releases are rarely final.

Automated Streams vs. Human Maintenance

Not all churn is created equal. While 6,630 distinct servers received updates, just two publishers accounted for 46.3% of all version change rows. One single publisher was responsible for 341 of the servers that updated on six or seven of the seven comparison days. This highlights a bifurcated ecosystem: a small number of automated, high-frequency release streams sitting atop a wide base of occasional, human-maintained updates. For developers, this means the 'latest' tag is dominated by automation, not necessarily stability or feature maturity.

The Deprecation Blind Spot

Version numbers do not tell the whole story. The data reveals 207 status changes, all moving from 'active' to 'deprecated,' with none reversing direction. A critical insight here is that 137 of these deprecations occurred on a single day, October 31, driven by one publisher's decision. Because these changes happened at the same version number, they were initially missed by standard version-watching tools. ProtocolProbe had to patch its own logic on October 29 to catch these silent deprecations, proving that watching only for version bumps leaves you vulnerable to sudden API or protocol withdrawals.

Key Takeaways

  • Poll frequently: The registry averages ~650 new servers and ~1,600 version updates per day; use the updated_since filter to track changes.
  • Pin exact versions: With 12,973 version updates in a week, relying on 'latest' is risky; lock dependencies to specific, tested versions.
  • Monitor status fields: Deprecations can occur without a version change, so your monitoring must check status flags, not just release tags.
  • Assume impermanence: No removed entry returned during the observation period, but listings can vanish or change status overnight without notice.

The Bottom Line

The MCP registry is currently a firehose, not a library. Until the ecosystem matures, developers must treat every dependency as ephemeral and pin aggressively, or risk having their agents break mid-deployment by a silent deprecation or a breaking change hidden in a minor version bump.