A weekly automated check of Python MCP servers revealed that 19% of them, totaling 932 packages, failed to start due to an SDK upgrade. The issue stems from the release of MCP SDK version 2.0.0, which changed module names and broke compatibility with packages that did not specify a version bound for the MCP dependency. While a simple fix of pinning the dependency to a version less than 2 resolves the issue for 88% of affected servers, a significant portion of these packages have outdated registry entries, meaning the actual number of broken projects may be lower than reported. AI
IMPACT This SDK upgrade issue highlights the fragility of package ecosystems and the importance of dependency management for AI development tools.
RANK_REASON The item describes a tool (mcpcost) used to test the compatibility of Python packages with an SDK upgrade, detailing the process and findings.
AI-generated summary · Google Gemini · from 1 sources. How we write summaries →