Unverified50% confidenceFactExact time
mcp-server-fetch's robots.txt check no longer targets only the initially requested URL but is re-checked after every redirect (GHSA-3jqg-r5pp-rmp2).
1
Sources
50%
Confidence
Long-term
Relevance
10/25/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedmcp-server-fetch fixes an issue in internationalized domain name (IDNA) scenarios where one form of a domain is checked but another form is connected to, potentially reaching internal network addresses (GHSA-v38p-wf49-hx2j).60% similarUnverifiedThe Fetch MCP server by default rejects private, loopback, and link-local addresses (including the cloud metadata endpoint 169.254.169.254), and re-checks the target IP on every redirect hop.60% similarUnverifiedReference has a built-in MCP Server that provides four dedicated tools: /search, /explain, /find_similar, and /check_doc_drift.58% similarUnverifiedclaude plugin validate now checks MCP server configurations, reporting .mcp.json entries that would be silently dropped, undeclared ${user_config.*} references, and unsafe URLs.58% similarUnverifiedThe MCP server exposes three tools: search_items (search by text and maximum price), get_item (get details by ID), and buy_intent (return a payment challenge by ID).57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1094937API
curl https://kongchang.com/api/v1/knowledge/claims/1094937MCP
get_claim(id=1094937)