Unverified50% confidenceFactExact time
MCP annotations are only requests to the client rather than guarantees, and actual behavior still needs to be clearly stated in server instructions.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn the MCP authorization flow, when rejecting a request, the server explicitly informs the client of the specific permission scope (Scope) that needs to be applied for.79% similarUnverifiedThe MCP protocol does not require clients to report clientInfo truthfully; the field is self-declared and there is no server-side verification mechanism.79% similarUnverifiedMCP uses a request-response model: after the client sends tools/call it waits for the server to return, with no progress pushed in between, and the protocol itself has no background execution semantics.76% similarUnverifiedThe MCP server must treat parameters coming from the Agent as untrusted external input, and must not assume they are safe just because the request comes from its own Agent.75% 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.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1045204API
curl https://kongchang.com/api/v1/knowledge/claims/1045204MCP
get_claim(id=1045204)