Unverified50% confidenceCautionExact time
An MCP server may only accept tokens issued for itself and must not forward client tokens to another API, as doing so would create a Confused Deputy vulnerability.
1
Sources
50%
Confidence
Long-term
Relevance
10/10/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe correct approach is for the MCP server to re-apply for a new dedicated token under its own identity when calling downstream services, rather than forwarding the incoming token.77% similarUnverifiedIn MCP, tokens obtained by a client are scoped to a single server and carry a single, narrow permission.75% similarUnverifiedThe current MCP specification supports HTTP Bearer Token as a transport-layer authentication mechanism, but makes no mandatory provisions regarding token issuance, binding of client identity, or server-side verification of token origin.74% 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.72% similarUnverifiedThe MCP specification requires that tool annotations be treated as untrusted unless the server is trusted.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/994264API
curl https://kongchang.com/api/v1/knowledge/claims/994264MCP
get_claim(id=994264)