NPM LIBRARY
@mcp-z/client
Official package-registry history. This page does not infer support or EOL from release activity.
- Versions indexed
- 27
- Latest version activity
- 2.3.0
- Latest registry signal
- Published
- Last synchronized
- 27 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.
| Version | Registry event | Signal | Release notes | Evidence |
|---|---|---|---|---|
| 2.3.0 | 20 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.2.4 | 20 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.2.3 | 12 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.2.2 | 9 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 1.3.0 | 8 Sep 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 2.2.1 | 8 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.2.0 | 8 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.1.0 | 8 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 1.2.1 | 6 Sep 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 2.0.1 | 6 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.0.0 | 6 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 1.2.0 | 5 Sep 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.1.1 | 31 Aug 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.1.0 | 29 Aug 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.12 | 29 Aug 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.11 | 29 Aug 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.10 | 29 Aug 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.9 | 29 Aug 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.8 | 24 Aug 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.7 | 10 Jan 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.6 | 10 Jan 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.5 | 4 Jan 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.4 | 4 Jan 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.3 | 2 Jan 2026 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.2 | 29 Dec 2025 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.1 | 29 Dec 2025 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |
| 1.0.0 | 29 Dec 2025 | DEPRECATEDThe 1.x line has ended. Its final release is the 2.x code with compatibility aliases, so upgrading is usually just: npm install @mcp-z/client@latest | Checked, none published | Official event ↗ |