Unverified50% confidenceReleaseExact time
mcp-server-fetch version 2026.10.28 refuses autonomous fetching when robots.txt returns a 5xx; rejects IPv4-compatible IPv6 addresses (::/96); adds a --no-readability-js option; and requires readabilipy 0.3.0, among other changes.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/28/2026
First Seen
Valid until: 1/26/2027
Sources
Related Entities
Related Claims
Unverifiedmcp-server-fetch now rejects NAT64 requests in the 64:ff9b::/96 range that encapsulate private, loopback, or link-local IPv4 addresses (GHSA-66qx-2266-pmj6).76% similarUnverifiedThe IPv6 address 2001:db8::1 is expanded to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa in ip6.arpa reverse resolution.65% similarUnverified127.0.0.1 is the loopback address in IPv4, and a service bound to that address only accepts connections from the same machine and cannot be accessed from the LAN or the public internet; listening on 0.0.0.0, by contrast, accepts connections from all network interfaces.63% similarUnverifiedVersion 1.2.3 removes code paths related to the retired IPEX (Intel Extension for PyTorch) backend (#39649).54% similarUnverifiedv0.5 adds operation options such as Block IP address and Leave the process alone to the connection table.53% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1109568API
curl https://kongchang.com/api/v1/knowledge/claims/1109568MCP
get_claim(id=1109568)