Unverified50% confidenceFactExact time
The MCP specification requires that tool annotations be treated as untrusted unless the server is trusted.
1
Sources
50%
Confidence
Long-term
Relevance
10/8/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe tool has a built-in function for pinning MCP tool definitions, and issues a warning when a connected MCP server subsequently modifies its tool definitions.78% 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.77% similarUnverifiedInternal company MCP services often require no authentication in order to emphasize speed, while MCP tools published externally and facing the public network typically require authentication based on encryption methods such as JWT.76% 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.75% similarUnverifiedThe MCP protocol itself does not carry risk semantics for tools, and the responsibility for security judgment falls back on the application developers.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/988964API
curl https://kongchang.com/api/v1/knowledge/claims/988964MCP
get_claim(id=988964)