# LLMIntel Model Lifecycle (remote · llmintel.ai)

Check whether an LLM model id is deprecated, retiring, or retired, and what to migrate to.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `llmintel.ai`: 69/100 (this document), [markdown](https://verifymcp.io/servers/ai-llmintel-model-lifecycle/v1-mcp.md), [page](https://verifymcp.io/servers/ai-llmintel-model-lifecycle/v1-mcp)
- npm · `@llmintel/mcp`: 46/100, [markdown](https://verifymcp.io/servers/ai-llmintel-model-lifecycle/llmintel-mcp.md), [page](https://verifymcp.io/servers/ai-llmintel-model-lifecycle/llmintel-mcp)

## Channel facts

- Endpoint: `https://llmintel.ai/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 386 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-llmintel-model-lifecycle https://llmintel.ai/v1/mcp
```

### Codex

```toml
[mcp_servers.ai-llmintel-model-lifecycle]
url = "https://llmintel.ai/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-llmintel-model-lifecycle": {
      "type": "remote",
      "url": "https://llmintel.ai/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-llmintel-model-lifecycle --url https://llmintel.ai/v1/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-llmintel-model-lifecycle:
    url: "https://llmintel.ai/v1/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 69, +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.

### 2026-08-01 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-28 (score 66)

First indexed and scored.

## MCP tools (5)

### `check_model` (~116 tokens)

Check a model's lifecycle status

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.

Input parameters:

- `model` (string, required): Model id or alias exactly as it appears in code, e.g. 'gpt-4o'.

### `list_retiring_models` (~76 tokens)

List models retiring soon

List tracked models scheduled to retire within a time window, soonest first. Use this to audit a codebase or plan migration work.

Input parameters:

- `provider` (string): Restrict to one provider. Omit for all providers.
- `withinDays` (integer): Only include models retiring within this many days. Defaults to 180.

### `suggest_replacement` (~56 tokens)

Suggest a replacement for a model

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.

Input parameters:

- `model` (string, required): Model id or alias to find a replacement for.

### `search_models` (~73 tokens)

Search the model catalog

List tracked models, optionally filtered by provider and lifecycle state. Use this to discover what is currently available from a provider.

Input parameters:

- `limit` (integer): Maximum results.
- `provider` (string): Filter by provider.
- `state` (string): Filter by canonical lifecycle state, e.g. 'active' or 'deprecated'.

### `recent_lifecycle_changes` (~65 tokens)

Recent lifecycle changes

Lifecycle state changes across all tracked providers, newest first. Use this to answer 'what model deprecations happened recently?'.

Input parameters:

- `provider` (string): Restrict to one provider.
- `sinceDays` (integer): Look back this many days. Defaults to 30.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-llmintel-model-lifecycle/v1-mcp#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 69
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 67
- 2026-07-29: 67
- 2026-07-28: 66

## Links

- Remote endpoint: https://llmintel.ai/v1/mcp
- Repository: https://github.com/hivemindunit/llmintel-mcp
- Website: https://llmintel.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-llmintel-model-lifecycle/v1-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-llmintel-model-lifecycle/v1-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-llmintel-model-lifecycle/v1-mcp