Is @modelcontextprotocol/inspector safe?
2 fixed advisories Facts from the mcp-audit registry about the npm package @modelcontextprotocol/inspector. The same data is served as JSON.
Check it from your terminal
mcp-audit vet @modelcontextprotocol/inspectorOffline: it uses the registry bundled with mcp-audit. mcp-audit update-registry fetches the newest one.
Registry facts
| Maintainer | Anthropic |
|---|---|
| Verified publisher | yes |
| Entry last checked | 2026-08-22 |
| Hash pins | none recorded |
| Provenance expected | yes; a missing Sigstore attestation is reported (ATTEST-013) with --verify-signatures |
| Repository | https://github.com/modelcontextprotocol/inspector |
Recorded advisories 2
| Advisory | CVSS | Summary | Fixed in |
|---|---|---|---|
| CVE-2025-49596 | not recorded | MCP Inspector proxy server lacks authentication between the Inspector client and proxy | 0.14.1 |
| CVE-2025-58444 | not recorded | MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server | 0.16.6 |
Advisories with no recorded fix are listed first. CVE IDs link to NVD, GHSA IDs to GitHub and other IDs to OSV. A fixed advisory affects only versions below its fix; vet exits 1 only for advisories with no fix.
What it can do
No capability tags are recorded for this package yet.
Check how you run it
This page describes the public package. What matters is your setup: which version you pin, which secrets you pass, and which other servers sit next to it.
mcp-audit checkBadge for your README
mcp-audit2 fixed CVEs
Preview drawn by this page. The real badge is rendered by shields.io from this JSON and updates when the registry does.
[](https://mcp-audit.dev/servers/npm/at-modelcontextprotocol-inspector/)