2.13.0

Security: Node.js runtime advisories (October 2026)

On October 20, 2026, eMudhra disclosed that the private keys for eight of its intermediate CA certificates could be recovered from the public certificates. On October 21, Node.js shipped security releases that update its bundled CA certificates for the compromise. The same releases fix several unrelated high-severity runtime CVEs, including DNS name truncation, TLS hostname checks on non-canonical IP addresses, and an out-of-bounds write in the Brotli decoder.

How this release stands

• The Inspector relies on the Node.js runtime for certificate checks. It ships no CA certificates of its own and doesn't opt into the system trust store. Every HTTPS connection it makes, to MCP servers and to OAuth discovery and token endpoints, is verified by the Node.js it runs on.
• The Docker image needs no action. ghcr.io/modelcontextprotocol/inspector:2.13.0 runs Node.js 22.23.4, a patched release, and contains no system CA store.
• This release also updates two of its own dependencies past published advisories: undici (#2812) and fast-uri (#2820).

If you run the Inspector from npm (npx or a global install)

It runs on your Node.js, which we can't update for you. Please run Node.js 22.23.4, 24.22.1 or 26.12.1, or later, and check with node --version. The package's engines field still accepts Node.js 22.19.0 and up, so npm won't warn you about an older, unpatched runtime. Node.js 20 and earlier are end-of-life, get no fix, and aren't supported by Inspector v2.

What's Changed

• feat(cli): --load-max-error-rate / --load-max-p99 thresholds set the exit code by @cliffhall in #2787
• feat(cli): --load-connections spreads a load run over many sessions by @cliffhall in #2791
• fix(auth): keep a static client's SEP-2352 issuer stamp across saves and restarts by @cliffhall in #2794
• docs(skills): document the v1 release procedure and advisory-fork merge constraints by @cliffhall in #2785
• feat(scripts): release:notes --advisory lists GHSA fixes and credits their reporters by @cliffhall in #2788
• test(cli): isolate the suite's default catalog from ~/.mcp-inspector by @cliffhall in #2793
• chore(web): restrict the dev Vite server's CORS to the configured origins by @cliffhall in #2789
• Warn on non-loopback web binds and document the token's access-control boundary by @cliffhall in #2790
• fix(auth): read a DCR secret stamped for another client as absent (#2768) by @cliffhall in #2792
• feat(cli): carry 429 retry timing in the CLI and mcpdo error envelopes by @cliffhall in #2795
• feat(web): sort the Tools list by displayed label (#2782) by @cliffhall in #2798
• feat(mcpdo): add tools/call --load on the shared load engine by @cliffhall in #2786
• fix(web): keep a failed connect's reason on the server card (#2783) by @cliffhall in #2801
• chore(cli): migrate the CLI bundle from tsup to tsdown by @cliffhall in #2803
• fix: guard OAuth destinations against link-local and metadata addresses in every client by @cliffhall in #2796
• chore(deps): upgrade the MCP TypeScript SDK to 2.4.0 by @cliffhall in #2799
• chore(build): migrate the web runner, mcpdo and TUI bundles from tsup to tsdown by @cliffhall in #2807
• feat(mcpdo): --load-connections and --load-max-* thresholds for tools/call --load by @cliffhall in #2806
• chore(skills): take SEP-2640 constants and schemas from the SDK, move the rest to core/extension/skills by @cliffhall in #2808
• feat(auth): opt-in scope on OAuth token refresh via scopeForRefresh (Entra AADSTS90009) by @cliffhall in #2809
• Release 2.13.0 step 1: audit fixes and bump to 2.13.0 on v2/main by @cliffhall in #2815
• fix(core): a deliberate disconnect no longer ends in "error" (#2817) by @cliffhall in #2819
• fix(deps): update fast-uri to 3.1.9 past four moderate advisories (#2820) by @cliffhall in #2821
• chore(release): merge v2/main into main for v2.13.0 by @cliffhall in #2818

Full Changelog: 2.12.0...2.13.0
Smoke test ledger for milestone branch: v2/chore/milestone-merge-v2.13.0

Thanks for helping us improve

This release addresses issues reported by these community members. Thank you for taking the time to file them:

• @aurelium (#2782)
• @tarun-amagian (#2783)