Your pinned MCP server may not be as pinned as you think

An MCP server configured to run one fixed release on an administrator's workstation ran with 15 different sets of dependencies over five weeks with its configuration untouched, according to James Lagermann, Director of Technical Alliances at Corelight, who found the drift in his company's lab. Twenty-three of the server's 69 packages changed versions, including the cryptography library, the JSON Web Token library and the MCP software development kit itself. The finding shows that pinning an MCP server's version does not pin its transitive dependencies, a supply-chain risk for AI coding assistants that rely on Model Context Protocol servers.