MCP Server CVE Exposure Mapping and Public API Released
MCP Server Security Analysis and Public API
Security researchers have analyzed thousands of MCP (Model Context Protocol) servers to map their dependency trees against known CVEs and security advisories. When you install an MCP server, you're inheriting its entire dependency tree, which may contain vulnerabilities.
Key Findings from the Analysis
- A meaningful percentage of servers carry known vulnerabilities
- Some servers accumulate dozens or 100+ CVEs through dependencies
- Severity varies significantly - high CVE count doesn't necessarily mean high risk, and low count doesn't guarantee safety
- Dependency sprawl is common across MCP servers
- A large portion of these servers still appear on major MCP directories
Public API Details
The researchers built a public API that requires no API key: https://api.mistaike.ai/api/v1/public/cve-index
With this API, you can:
- Search by repository name or server name
- Filter results by vulnerability severity
- Sort by CVE count or recency of vulnerabilities
Important Caveats
The presence of a CVE doesn't automatically mean it's exploitable. Some vulnerabilities exist in unused code paths, while others may already be mitigated. This tool provides visibility into supply chain risk rather than labeling projects as unsafe.
Next Phase: Runtime Behavior Analysis
The researchers are now analyzing what MCP servers actually do at runtime, including network calls and external dependencies. In a subset of servers analyzed so far (~5%), they've identified a small number of behaviors that may have privacy implications, including apparent use of invisible Unicode characters consistent with response watermarking. These observations are still under review, and the team is working to separate true positives from analysis artifacts before engaging with projects directly.
📖 Read the full source: r/ClaudeAI
👀 See Also
Strict Read-Only Rules in Skill Files Are Instructions, Not Enforcement
A Reddit user reports an OpenClaw agent with a strict 'READ-ONLY — never post' rule was tricked into posting via prompt injection, highlighting that skill file rules are just instructions, not enforced constraints.
Audio-Layer Prompt Injection Against Claude: What's Not in the Transcript
A builder of a prompt injection detection API shares findings on audio-layer attacks against Claude, revealing that attacks in the signal (not transcript) are invisible in logs and pose a real threat to voice agents.
U of T Researchers Demonstrate AI Worm Powerable by Free Open-Weight Models
Researchers at the University of Toronto demonstrated the first AI-powered worm that adapts its spreading strategy using publicly accessible open-weight models, targeting any online device.
Sandboxing Local AI Agents with Firecracker MicroVMs
A developer created a sandbox that isolates AI agent execution inside Firecracker microVMs running Alpine Linux, addressing security concerns about agents running commands directly on the host machine. The setup uses vsock for communication and connects to Claude Desktop through MCP.