Unverified50% confidenceSolutionExact time
mcp-server-fetch rejects private addresses, loopback addresses, and metadata addresses by default as an SSRF protection measure.
1
Sources
50%
Confidence
Long-term
Relevance
10/11/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe malicious MCP server disguised itself as an email-sending server with the same name as an official one, functioned normally, but secretly BCC'd every email to a third party.72% similarUnverifiedWhen a client calls a protected MCP server without a token, it receives 401 Unauthorized, and the response header indicates the resource metadata link and the required scope.69% similarUnverifiedMCP can perform permission control, for example by intercepting the Delete keyword in database requests and rejecting them outright.68% similarUnverifiedGoose grants trust by default to MCP servers manually added by users, so a write tool falsely labeled as read-only will be executed directly without any confirmation.63% similarUnverifiedBlindly forwarding tokens should be avoided, as tokens are typically bound to a specific audience; tokens issued to an MCP server that are forwarded as-is to a downstream API may introduce security vulnerabilities or privilege escalation.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/995554API
curl https://kongchang.com/api/v1/knowledge/claims/995554MCP
get_claim(id=995554)