LLMIntel Model Lifecycle
REMOTE · LLMINTEL.AI · 2 COMPONENTS
Check whether an LLM model id is deprecated, retiring, or retired, and what to migrate to.
Available components
Last scanned (1 hour ago)
Scores higher than 97% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 −2
- Stability: pass → 0.87 functional
- Server version: 0.2.0 → 0.2.1 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 · Probed https://llmintel.ai/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=llmintel.ai | CN=YR2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | RSA 2048 | SHA256-RSA | 655562a65ca0f21ea9a55aef13e80036e90 |
| SANs: llmintel.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of llmintel.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| llmintel.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://llmintel.ai/v1/mcp | Verified | 200 | |
| http (plaintext) | http://llmintel.ai/v1/mcp | HTTPS enforced | 308 | https://llmintel.ai/v1/mcp |
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 is a hosted endpoint at https://llmintel.ai/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · llmintel.ai
claude mcp add --transport http ai-llmintel-model-lifecycle 'https://llmintel.ai/v1/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 hosted endpoint (https://llmintel.ai/v1/mcp).
Is the LLMIntel Model Lifecycle MCP server safe to use?
LLMIntel Model Lifecycle scores 89 out of 100 on VerifyMCP. 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.
Does the LLMIntel Model Lifecycle MCP server require authentication?
No. We connected to LLMIntel Model Lifecycle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.