MCP Inspector fixed seven more security flaws in November. Update it first.
By Lior AharonovFounder, 7IT Solutions ·
What happened
MCP Inspector 2.14.0 on 4 November 2026 fixed three vulnerabilities and 2.15.0 on 12 November fixed four more, per their release notes. They include an MCP App that could leave its sandbox frame policy and a fetch guard that missed some cloud metadata addresses. The 1.x line got its own security fixes in 1.0.4 and 1.0.5.
Why it matters
Inspector is the tool you point at a server you do not trust yet. An unpatched copy lets that server reach further than the test you meant to run.
What to do
Run npx @modelcontextprotocol/inspector@latest, or @v1-latest on the 1.x line, and remove older copies pinned in scripts or docs.

My take
Lior Aharonov
Founder, 7IT Solutions
A testing tool meets the worst servers first, so it gets patched first.
Sources
| MCP Inspector 2.15.0 release notes | github.com |
| MCP Inspector 2.14.0 release notes | github.com |
Researched with AI tools; every fact is checked against the linked sources.