Unverified60% confidenceFactExact time
A security audit conducted this year found that approximately one quarter of publicly available MCP servers have absolutely no authentication whatsoever.
2
Sources
60%
Confidence
Medium-term (~90 days)
Relevance
9/27/2026
First Seen
Valid until: 12/26/2026
Sources
Related Entities
Related Claims
UnverifiedThe MCP ecosystem is still in its early stages and lacks mature signing, permission declaration, and auditing standards; third-party MCP server origins are hard to verify, and tool descriptions may be maliciously tampered with to induce model invocation (i.e., "tool poisoning").75% similarUnverifiedCurrent public information about the JobRunner MCP server does not cover key details such as permission control, operation auditing and the risk of erroneous rescue; the security boundaries await further clarification in official documentation.73% similarUnverifiedMCP itself is not a complete security system; secure deployment still requires authentication, fine-grained authorization, encryption, sandboxing, observability, and human approval for sensitive operations.72% similarUnverifiedAnnotation declarations on MCP servers have no enforcement validation mechanism at the protocol level, creating a supply-chain trust problem where an attacker can publish a malicious server claiming to be read-only while performing arbitrary write operations.70% similarUnverifiedCritics point out that an MCP Server with file system write permissions, once exploited by malicious tools, would present an attack surface harder to audit than traditional API integrations68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/953112API
curl https://kongchang.com/api/v1/knowledge/claims/953112MCP
get_claim(id=953112)