LLMIntel Model Lifecycle
NPM · @LLMINTEL/MCP · 2 COMPONENTS
Check whether an LLM model id is deprecated, retiring, or retired, and what to migrate to.
Available components
Last scanned (10 hours ago)
Scores higher than 92% of npm servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hivemindunit/llmintel-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 386 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −3
- Stability: pass → 0.83 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@llmintel/mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | hivemindunit/llmintel-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/hivemindunit/llmintel-mcp/.github/workflows/publish.yml@refs/tags/v0.2.0 |
| Rekor log index | 2265541100 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1499c67f08952bb2cf9235c426adb3f4107a38b2dcc696808a598131c459652fd9b516a747256807ef7224c32cfdd604315fb3a0d74e057fa17702d6a |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_model Check a model's lifecycle status ~116
Check whether an LLM model id is safe to use, deprecated, or retired, and what to migrate to. Accepts the exact string used in code (e.g. 'gpt-4o', 'claude-sonnet-4-5-20250929', 'anthropic/claude-opus-4-1'). Call this before writing or changing any hardcoded model id.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Model id or alias exactly as it appears in code, e.g. 'gpt-4o'. |
No output schema declared.
No examples provided.
list_retiring_models List models retiring soon ~76
List tracked models scheduled to retire within a time window, soonest first. Use this to audit a codebase or plan migration work.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Restrict to one provider. Omit for all providers. |
| withinDays | integer | – | Only include models retiring within this many days. Defaults to 180. |
No output schema declared.
No examples provided.
recent_lifecycle_changes Recent lifecycle changes ~65
Lifecycle state changes across all tracked providers, newest first. Use this to answer 'what model deprecations happened recently?'.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Restrict to one provider. |
| sinceDays | integer | – | Look back this many days. Defaults to 30. |
No output schema declared.
No examples provided.
search_models Search the model catalog ~73
List tracked models, optionally filtered by provider and lifecycle state. Use this to discover what is currently available from a provider.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results. |
| provider | string | – | Filter by provider. |
| state | string | – | Filter by canonical lifecycle state, e.g. 'active' or 'deprecated'. |
No output schema declared.
No examples provided.
suggest_replacement Suggest a replacement for a model ~56
Given a deprecated or retiring model, return the provider's recommended replacement(s) and, when none is published, active models from the same provider to consider.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | Model id or alias to find a replacement for. |
No output schema declared.
No examples provided.
How do I install the LLMIntel Model Lifecycle MCP server?
LLMIntel Model Lifecycle runs locally as an npm package, launched with npx -y @llmintel/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @llmintel/mcp
claude mcp add ai-llmintel-model-lifecycle -- npx -y @llmintel/mcp
What is the LLMIntel Model Lifecycle MCP server?
LLMIntel Model Lifecycle is an MCP server listed in the public MCP registry as ai.llmintel/model-lifecycle. Check whether an LLM model id is deprecated, retiring, or retired, and what to migrate to. This page covers its npm package (@llmintel/mcp).
Is the LLMIntel Model Lifecycle MCP server safe to use?
LLMIntel Model Lifecycle scores 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LLMIntel Model Lifecycle MCP server expose?
LLMIntel Model Lifecycle exposes 5 tools: check_model, list_retiring_models, suggest_replacement, search_models, recent_lifecycle_changes. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.
Is the LLMIntel Model Lifecycle MCP server still maintained?
LLMIntel Model Lifecycle is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the LLMIntel Model Lifecycle MCP server under?
LLMIntel Model Lifecycle declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.