Source: github.com/modelcontextprotocol/servers/releases/tag/v2.1.0
The v2.1.0 release of the modelcontextprotocol/servers repository fixes eight vulnerabilities in three servers. Users of @modelcontextprotocol/server-filesystem and @modelcontextprotocol/server-everything should move to 2.0.1, and mcp-server-fetch users should move to 2026.10.24.
In the filesystem server, writes are kept inside the checked directory on Linux and macOS, even if a parent directory is swapped for a symlink mid-operation. Windows is only partly covered, and the advisory explains the remaining exposure and how to configure around it. The everything server's HTTP and SSE transports now check the Origin header and no longer send a wildcard Access-Control-Allow-Origin, so web pages can no longer call its tools.
In the fetch server, the host name used for the address check now matches the one the connection uses, and NAT64 addresses carrying private, loopback or link-local IPv4 addresses are refused. robots.txt is also rechecked after every redirect. Because the TypeScript servers moved from date versions to semantic versions in 1.0.0, package managers rank 2.0.1 below the 2025.x and 2026.x releases, so date-version users must install it explicitly.
Why it matters if you build agents
Agents that use these servers for file access, sandbox-style writes or web fetching should upgrade now rather than waiting for a package manager to offer the update. Pin the exact version, since npm will not offer 2.0.1 as an upgrade to date-versioned installs. On Windows, filesystem writes remain partly exposed, so review the advisory's configuration guidance before pointing the server at untrusted paths.
Get stories like this every weekday
One short email with the day's agent tooling news.