Unverified50% confidenceFactExact time
The 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedBefore initiating an outbound request, the MCP server must resolve and validate the target address itself, checking whether it resolves to internal IP ranges, cloud metadata endpoints, or other restricted resources.71% similarUnverifiedWhen constructing outbound requests, the MCP server directly uses the address provided by the Agent, without verifying where that address actually resolves to, which attackers can exploit to make the server access internal networks, cloud metadata interfaces, or other sensitive resources.71% similarUnverifiedIn the OAuth flow, the MCP server returns a 401 Unauthorized response to requests without a valid token, along with a login URL pointing to the authorization server.70% similarUnverifiedIn MCP over HTTP communication, when a client makes a call without a token, the server returns 401 Unauthorized.69% similarUnverifiedWhen an MCP server cannot reliably identify the client making a request, any entity that can reach that service endpoint may obtain data or invoke tools under the guise of a legitimate client.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1055044API
curl https://kongchang.com/api/v1/knowledge/claims/1055044MCP
get_claim(id=1055044)