BlackTreeLifecycle intelligence
Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT

NPM LIBRARY

@modelcontextprotocol/inspector-cli

Official package-registry history. This page does not infer support or EOL from release activity.

Versions indexed
34
Latest version activity
1.0.2
Latest registry signal
Deprecated
Last synchronized
26 Sep 2026
Authoritative registry

Version entries link to the official registry catalogue event that supplied the record.

Open package on npm ↗
Lifecycle interpretation

Publication or deletion in a package registry is a distribution signal, not a promise of maintenance or security support. Any verified publisher EOL boundary remains in the main lifecycle catalogue.

Package-version activity

Newest official registry events first.

34 records
VersionRegistry eventSignalRelease notesEvidence
1.0.224 Aug 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
1.0.128 Jul 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
1.0.018 Jul 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.22.04 Jun 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.21.214 Apr 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.21.127 Feb 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.21.024 Feb 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.20.09 Feb 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.19.023 Jan 2026DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.18.016 Dec 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.17.54 Dec 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.17.222 Oct 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.17.113 Oct 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.17.01 Oct 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.818 Sep 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.712 Sep 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.63 Sep 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.518 Aug 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.415 Aug 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.311 Aug 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.225 Jul 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.110 Jul 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.16.09 Jul 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.15.029 Jun 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.14.318 Jun 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.14.214 Jun 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.14.113 Jun 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.14.04 Jun 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.13.021 May 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.12.013 May 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.11.030 Apr 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.10.217 Apr 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.10.117 Apr 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗
0.10.017 Apr 2025DEPRECATEDv1 is deprecated. Upgrade to v2: npm i @modelcontextprotocol/inspector@latest. v1 gets security fixes only, published under the v1-latest tag.Checked, none publishedOfficial event ↗