Security Audit Finds Anthropic's MCP Reference Servers Vulnerable, Introduces Hallucination-Based Vulnerabilities

MCP Server Security Audit Results
A comprehensive security audit of 100 Model Context Protocol (MCP) server packages revealed significant security issues. The audit found that 71% of servers scored an F, with zero servers receiving an A grade. This includes Anthropic's own reference implementations that are often considered the "Gold Standard."
Hallucination-Based Vulnerabilities (HBVs)
The audit identified a new class of vulnerability called Hallucination-Based Vulnerabilities. When MCP tools have vague descriptions (like "manages files"), Claude is forced to guess parameters. This creates both security vulnerabilities and token waste as Claude enters "reasoning loops" trying to determine tool boundaries, burning through context windows and message limits.
Specific Findings
- The Reference Trap: Official servers for GitHub and filesystems—the ones Anthropic recommends—scored 0/100 on baseline security tests. These servers allow "unbounded" inputs, meaning prompted agents can be tricked into deleting or exfiltrating data due to lack of internal safety guardrails.
- RCE-Class Risks: The audit identified structural precursors to RCE vulnerabilities similar to CVE-2025-68143 that previously affected the ecosystem.
- Authentication Limitations: Even with OAuth configured, poorly defined tools remain vulnerable. Sophisticated prompts can turn Claude into a tool for accidental or intentional data destruction.
Protection Recommendations
- Audit your servers: Don't trust servers just because they're in Anthropic's official repository.
- Harden your manifests: Ensure every tool has
minLength,maxLength, and strictpatternregex in its JSON schema. - Run the Scanner: Use the open-source audit tool:
npx @agentsid/scanner
Key Takeaway
Agentic setups are likely "vulnerable by default" because official templates prioritize flexibility over safety. Properly hardening tool definitions can both protect data and reduce token consumption by preventing unnecessary reasoning loops.
The full white paper and methodology are available at: https://github.com/stevenkozeniesky02/agentsid-scanner/blob/master/docs/state-of-agent-security-2026.md
📖 Read the full source: r/ClaudeAI
👀 See Also

ClawVault Security Enhancement Adds Sensitive Data Detection for OpenClaw
A new enhancement to ClawVault adds real-time sensitive data detection and automatic sanitization for OpenClaw API traffic, intercepting plaintext passwords, API keys, and tokens before they reach LLM providers.

Free Claude Skill Scans Other Skills for Security Risks
A developer has built a free Claude skill that reviews the security of other Claude skills by checking code for potentially malicious behavior and analyzing repositories with a scorecard-style approach. The tool helps answer whether a Claude skill appears reasonably safe to use.

OpenClaw Security Breach: CEO's Agent Sold for $25K, 135K Instances Exposed
A UK CEO's OpenClaw instance was sold for $25,000 on BreachForums, exposing plain-text Markdown files containing conversations, production databases, API keys, and personal details. SecurityScorecard found 135,000 OpenClaw instances exposed with insecure defaults.

OpenClaw Slack Security: API Key Exposure Risks and Fixes
OpenClaw Slack deployments can expose API keys through error messages in channels, with over 8,000 instances found exposed in a Bitsight report. The source details three specific vulnerabilities and provides practical fixes including system prompt modifications and SlackClaw migration.