2026.10.10 → 2026.10.19
date version, 19 October 2026fetch: input schema changed
MCP servers / mcp-server-fetch
mcp-server-fetch
2 of its last 2 updates changed what the agent reads: 0 tool descriptions rewritten, up to 2026.10.19.
PyPI package · PyPI page · recorded on 24 October 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. Method and limits.
Release by release
2026.8.18 → 2026.10.10
date version, 11 October 2026fetch: input schema changed
Releases tried: 2025.4.7 (2025-04-07), did not start; 2026.6.4 (2026-06-04), did not start; 2026.7.10 (2026-07-10), did not start; 2026.8.18 (2026-08-18); 2026.10.10 (2026-10-11); 2026.10.19 (2026-10-19).
Tools in 2026.10.19
The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition.
| Tool | Description | Pin |
|---|---|---|
| fetch | Fetches a URL from the internet and optionally extracts its contents as markdown. Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that. | 1ac44effa028 |
Lock these tools
Pin what mcp-server-fetch serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.
$ pip install verfy
$ verfy lock check --update # shows each tool, then writes verfy.lock
$ git add verfy.lock# .github/workflows/verfy.yml, after actions/checkout
- uses: anvarbekovjavohir277-dot/verfy-action@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.