MCP Inspector 2.14.0 repairs 3 vulnerabilities

On 4 November 2026, the project of MCP Inspector released version 2.14.0. MCP Inspector is a developer tool for MCP (Model Context Protocol) servers. Its release notes tell that it repairs 3 vulnerabilities from private reports. One of the 3 also has the vulnerability in the version 1 line, and version 1.0.4 repairs it there. The release notes give no severity rating.

What changed

• The proxy removes an app frame that tries to go out of the host page.
• When you add a server.json setup, the tool shows the correct command before you record it.
• A URL from a server opens only if it uses http or https.
• The tool shows a pattern above the limits as unverified.

The proof

The release notes give no test results. They show 3 repairs for version 2. Version 1.0.4 does not use server patterns. It accepts a value that does not agree with a pattern, and shows a message.

What is not known

The release notes give no severity and no wide range of versions with the vulnerabilities. They do not report an attack. They tell that the changes apply to the Inspector, not to all MCP tools.

Insight: Servers are now input that is not safe

In October 2026, Cycode found that an MCP server that an attacker controls can get OAuth credentials. AWS repaired 2 bugs in the MCP servers of AWS. At this time, the Inspector limits the data that a server can send. This reads as a move to see servers as input that is not safe, not as safe parts. Teams that connect to servers they did not make must test them with the new version.