MCP reference servers 2.2.0 adds fetch controls and security hardening

The MCP reference-server repository’s 2.2.0 release groups several package updates; it is not a single package version to apply everywhere.

Fetch and filesystem changes

Fetch gains --no-readability-js for extraction without Node.js. It refuses autonomous requests when robots.txt returns a server error and adds address filtering. The filesystem server reports hard-link counts and supports cross-filesystem moves by copying when the operating system returns EXDEV.

The Everything server masks credential-like environment values by default and checks non-public addresses on every redirect hop for its gzip resource tool.

An application update is not a runtime update

The release explicitly says npm-based TypeScript servers use the operator’s Node.js runtime. Its runtime and certificate-update guidance must therefore be handled separately from installing a server package. Existing Python fetch environments can likewise retain an older certificate bundle unless refreshed.

Published versions differ: Everything and Filesystem are 2.1.0, Memory is 2.0.1, and the Python Fetch, Git and Time packages use 2026.10.28. Sequential Thinking remains unchanged. Review the release’s package table and deployment-specific instructions rather than assuming every component was updated.

See the modelcontextprotocol-servers hub.