Unverified50% confidenceFactExact time
The MCP protocol does not require clients to report clientInfo truthfully; the field is self-declared and there is no server-side verification mechanism.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe MCP protocol itself has no native design for pagination, lazy loading, or cross-server search.78% similarUnverifiedThe MCP Client does not execute tools directly; it only serves the functions of translation and forwarding.78% similarUnverifiedThe new version of MCP introduces a Stateless Protocol, where the server no longer needs to maintain session context, and each request is independent and self-contained.77% similarVerifiedThe MCP protocol itself only defines communication specifications and does not guarantee complete semantic mapping of data.77% similarUnverifiedAn 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.77% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1034249API
curl https://kongchang.com/api/v1/knowledge/claims/1034249MCP
get_claim(id=1034249)