Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 3 min read

MCP quickstarts still show unpinned npx despite security guidance

The docs contradiction One docs issue says beginner examples should match the Local Server Security guidance by installing a specific version instead of using latest. For maintainers, the immediate check is whether eve

The docs contradiction

One docs issue says beginner examples should match the Local Server Security guidance by installing a specific version instead of using latest. For maintainers, the immediate check is whether every quickstart, examples page, and generated snippet enforces the same package-version rule as the security page, because conflicting guidance creates two operational standards inside the same documentation set. The same issue reports that docs/develop/connect-local-servers.mdx, docs/examples.mdx, docs/develop/build-client.mdx, and docs/tools/debugging.mdx start local servers unpinned, and it says this appears in both the 2026-07-28 and draft docs. That means this is not a single bad example to patch by hand; if your team copied MCP launchers from the docs, review every local server command path you ship, including build-client walkthroughs and debugging instructions. The proposed fix in that issue is specific: pin the package in args, such as @modelcontextprotocol/[email protected], and add a sentence that links readers to the security guide. If you maintain agent templates or local launcher JSON today, you do not need to wait for a docs merge to act: replace floating npx package references with explicit versions, then record where version bumps are reviewed so the next update is deliberate instead of accidental.

Operational impact

The issue warns that each unpinned launch can resolve to whatever package was published most recently. In practice, that turns a stable-looking MCP config into a moving dependency edge, so reproducibility, rollback, and incident review all get harder because the same command may not execute the same package over time. The same report says the registry already rejects latest and version ranges for server.json packages, leaving the docs as the main place that still teaches the unpinned form. For tool builders, a sensible response is to align local validation with that stricter registry posture now, for example by linting launcher commands for floating package refs during CI or before a config is checked in. The issue author also reports a sample result: among 2,999 public GitHub repositories examined, 159 of the 346 repositories that configure a local MCP server started at least one server with no pinned version, and the author states that this sample is not a census. Because that number is explicitly limited to what code search surfaced, the safe technical takeaway is not a market-wide rate but a prompt to scan your own repositories and examples for npx -y commands that omit a concrete package version.

Related docs drift

A separate documentation issue says several other documentation problems affect MCP specification version 2026-07-28 and, except for one listed item, also appear in the draft pages. That matters here because versioned pages and draft pages can drift together, so checking only one track is not enough when you are verifying security-sensitive examples against schema text, changelogs, and guidance pages. Another open security discussion says the specification leaves the enforcement question to each implementor and does not yet provide a shared account of what that enforcement should look like. My reading is that this raises the cost of documentation mistakes: when operational safeguards are largely implemented outside protocol enforcement, quickstarts and examples become part of the effective security boundary, so they should be reviewed with the same care as launcher code and validators.

Sources

Created with AIVE

This article was written with AIVE, our AI-powered publishing autopilot, from the cited public sources, and checked automatically before publication. OU1COMES reviews published articles and corrects or removes them when needed.

AIVE powers the intelligence. OU1COMES delivers the outcomes.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.