Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

NewsResearch

Corelight: a pinned MCP server can still pull fresh dependencies on every launch, so pinning the server does not pin what runs

James Lagermann of Corelight launched MCP servers in a lab with one-line package runners, each pinned to an exact release, version or commit. For one community server the launcher ignored its hash-pinned lock file and resolved about 60 dependencies fresh from PyPI whenever the environment was rebuilt: over five weeks, with no config change, it ran 15 different dependency sets and 23 of 69 packages changed version, including cryptography, a JWT library and the MCP SDK. Of 35 MCP servers reviewed from two vendor catalogs and the lab, 23 had a recommended install that pulls from a public registry on each launch or install, and several vendors' setup instructions start a local proxy with an npx "@latest" tag. No compromise is reported. Five servers frozen to a commit and installed once from a hash-pinned lock file stayed identical over 457 launches. Corelight's advice: pin to a commit, install from the lock file with hash checking, launch the installed server directly and turn off update checks at startup. Lagermann notified the maintainers; one agent exchange changed its review process.

Why it matters

An MCP server runs with your assistant's access. If its dependencies change every time it starts, the code you approved is not the code that runs.

Sources

Read it with the rest of the news in the Learning Center