Check the MCP reference server security release

The MCP reference servers' v2.1.0 release includes security fixes for Filesystem, Everything and Fetch. The repository release number differs from each published package version. ^[1]

Check the installed packages

That release lists these patched packages: ^[1]

@modelcontextprotocol/server-filesystem: 2.0.1.
@modelcontextprotocol/server-everything: 2.0.1.
mcp-server-fetch: 2026.10.24.

The TypeScript packages changed from date versions to semantic versions. Package managers sort 2.0.1 below a 2026.x version, so an ordinary upgrade check can miss the fix. The release gives this explicit installation example: ^[1]

bash

npm install @modelcontextprotocol/server-filesystem@2.0.1

These are the versions in that security release, not a claim that they will remain the newest. Check subsequent releases before changing an existing installation. ^[1]

Review what changed

The release fixes filesystem path handling, HTTP request handling in Everything, and Fetch checks involving internal addresses and redirected robots.txt requests. Read its linked advisories for the affected paths. ^[1]

Check the Windows limitation

The filesystem advisory says version 2.0.1 anchors writes to the validated directory on Linux and macOS. On Windows, a concurrently replaced directory junction can still redirect certain writes outside the allowed folders. ^[2]

The advisory recommends avoiding allowed directories that another user or an untrusted local process can write to on Windows. Do not treat a package update as removal of that documented limitation. ^[2]

After updating, review the package referenced by your client's actual launch configuration and restart the client. A separate package installation does not prove an existing process is running the new version.