Unverified50% confidenceTradeoffExact time
MCP servers face requests driven by natural language, where the requests themselves have no cryptographically verifiable origin, making the confused deputy problem particularly acute in agent scenarios.
1
Sources
50%
Confidence
Long-term
Relevance
10/11/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen 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.80% similarUnverifiedCommon anti-patterns for MCP servers include excessive authorization, lack of request source validation, hardcoding sensitive credentials on the server side, and insufficient filtering of instructions passed in by agents.79% similarUnverifiedUnder the old MCP specification, GitHub MCP and many distributed MCP servers could not support elicitation, because it requires cross-server communication to coordinate state and sessions.72% similarUnverifiedMCP server spoofing attacks exploit the assumption in the protocol design that servers are trusted by default, rather than exploiting vulnerabilities in the traditional sense.71% similarUnverifiedClients and servers written against the old MCP specification will be unable to communicate normally with the new specification, and code paths that rely on session state, handshake flows, or stream resumability may break.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/997347API
curl https://kongchang.com/api/v1/knowledge/claims/997347MCP
get_claim(id=997347)