docs(mcp-server): pin npm version, remove -y flag — SAFE-MCP NEW-003 - #18
Merged
Merged
Conversation
…EW-003) - Quick start install example: add @1.0.0 version pin - .mcp.json Configure example: pin to @1.0.0, remove -y auto-accept flag - Add Callout warning explaining why pinning is required (unpinned + -y = arbitrary code execution on package compromise) with link to npm page - Troubleshooting: update standalone run example to use pinned version Addresses SAFE-MCP finding NEW-003 (HIGH) from SAFE-MCP audit (PR #808). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the MCP server quickstart docs to reflect the pinned-version security recommendation from the SAFE-MCP audit (PR #808, finding NEW-003 HIGH).
Changes to
content/docs/mcp-server.mdxnpx @molecule-ai/mcp-server→npx @molecule-ai/mcp-server@1.0.0.mcp.jsonconfigure example:["-y", "@molecule-ai/mcp-server"]→["@molecule-ai/mcp-server@1.0.0"]— removes the-yauto-accept flag and pins to the current stable release<Callout type="warn">added immediately after the configure example explaining:-y= silent arbitrary code execution risk on package compromise@1.0.0Security context
SAFE-MCP finding NEW-003 (HIGH severity): both
@molecule-ai/mcp-serverand related packages ran vianpx -ywith no version pin. If either package were compromised on npm, the next MCP client restart would silently execute the attacker's code with full MCP permissions.This is a low-effort, high-value fix: just pin the version and drop
-y.Pairs with
Monorepo PR #808 —
docs(security): SAFE-MCP audit report 2026-04-17 (closes #747). The full audit report is internal; this PR captures the single actionable change for public MCP users.Test plan
.mcp.jsonexample no longer contains-y@1.0.0appears in all three code blocks (install, configure, troubleshooting)<Callout type="warn">renders correctlyhttps://www.npmjs.com/package/@molecule-ai/mcp-server)🤖 Generated with Claude Code