MCP reference servers 1.0.0: a release ledger, not a safety badge
Today’s Extensions digest checks the fetch component, seven package versions and a mixed-license repository. No package was run.
October 12, 2026 source check
Today’s Extensions digest checks the fetch component, seven package versions and a mixed-license repository. No package was run. v1.0.0
One release, two version schemes
The official October 11 release lists Everything, Filesystem, Memory and Sequential Thinking at 1.0.0 on npm. Fetch, Git and Time are listed at 2026.10.10 on PyPI. Those are package versions; do not read the tag as a new protocol specification. The repository calls these reference implementations. My reason to feature this release is the changed access boundary in Fetch, not the round number.
Focus: mcp-server-fetch
Fetch retrieves a URL and converts HTML to Markdown for an LLM. The documented tool has url, max_length, start_index and raw arguments; max_length defaults to 5,000 characters and start_index to zero. That chunking interface helps control the returned text, but it is not a destination policy. A short response can still come from a sensitive host. The package’s current description says it uses MCP Python SDK 1.x, with mcp>=1.29.0,<2, and requires Python 3.10 or newer.
Setup: inspect before starting
The documentation offers uvx mcp-server-fetch or pip install mcp-server-fetch, followed by python -m mcp_server_fetch. These are source-documented launch paths, not commands I executed. For a controlled rollout, resolve and record the exact package version rather than assuming an unpinned invocation gives the reviewed build. Confirm the running server identifies as 2026.10.10. A local stdio server is still code on your machine, with the network reach that environment permits.
Maintenance and observed community signal
The release record is dated October 11, 2026; the network-guard PR was merged October 5. The repository page displayed 91,128 stars when checked October 12. That is a repository-wide signal, not Fetch usage or approval of this version, and popularity is not quality. I make no claim about growth, download trends or a ranking. Maintenance evidence here is a published release and a merged change, not proof that every deployment is maintained.
License: keep the component and repository separate
The Fetch package metadata declares MIT. The repository LICENSE describes a transition: new code and specification contributions use Apache-2.0, documentation contributions other than specifications use CC-BY-4.0, and earlier contributions without relicensing consent remain MIT. Therefore, calling the entire current tree simply MIT would hide a material distinction. For redistribution, inspect the files and notices of the exact artifact you use. This digest reports the source declarations; it is not a legal opinion about your distribution.
Security and privacy: changed defaults, remaining limits
PR #5033 and the live package description document refusal of non-public addresses before requests, including robots.txt and every redirect hop. --allow-private-ips disables that guard. Two stated limits remain: DNS can change between the guard’s resolution and the connection, and names the server cannot resolve itself are passed through, including names only a proxy can resolve. My recommendation is to keep network egress controls independent of the URL check, use a secret-free environment for acceptance tests, and treat retrieved page text as untrusted data. The destination sees the request; do not put private material in URLs.
A small review workflow
Create a release ticket with four evidence fields: exact installed version; startup arguments and proxy; refusal results for a controlled loopback test and a controlled public-to-loopback redirect; and the actual connection’s network policy. Keep vendor-reported tests separate from your observations. Recheck the license of the pinned artifact before redistribution. Do not use the bypass flag merely to make a failed test turn green. This is a review plan, not an audit result or a claim that I tested these servers.
Documented launch paths, not executed here
uvx mcp-server-fetch
# alternative
pip install mcp-server-fetch
python -m mcp_server_fetchSource ledger and a packaging caveat
The fetched project-page rendering still displayed 2026.8.18. The live PyPI JSON endpoint, checked separately on October 12, returned 2026.10.10 and the new guard description, consistent with the release ledger. I used that live package metadata to resolve the mismatch, rather than pretending the first rendering was current. PyPI JSON