LLMIntel Model Lifecycle
REMOTE · LLMINTEL.AI · 2 COMPONENTS · SCANNED AUG 3
Check whether an LLM model id is deprecated, retiring, or retired, and what to migrate to.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability81
- 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 Management20
- Stability observed for 6 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · llmintel.ai
claude mcp add --transport http ai-llmintel-model-lifecycle https://llmintel.ai/v1/mcp
[mcp_servers.ai-llmintel-model-lifecycle] url = "https://llmintel.ai/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-llmintel-model-lifecycle": {
"type": "remote",
"url": "https://llmintel.ai/v1/mcp",
"enabled": true
}
}
} openclaw mcp add ai-llmintel-model-lifecycle --url https://llmintel.ai/v1/mcp --transport streamable-http
mcp_servers:
ai-llmintel-model-lifecycle:
url: "https://llmintel.ai/v1/mcp" {
"mcpServers": {
"ai-llmintel-model-lifecycle": {
"type": "http",
"url": "https://llmintel.ai/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 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
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Jul 26 66
First indexed and scored.
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 3 Aug 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 | 30 Jun 2026 | 28 Sept 2026 | RSA 2048 | SHA256-RSA | 597569372cb71e3a259588bd7b97cdd9344 |
| 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 |
DNSSEC insecure
Validation of llmintel.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 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 |
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.
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.