Lets an AI agent check if LLM model IDs are deprecated or retired and find recommended replacements across major providers.
Also known as hivemindunit/llmintel-mcp, model-lifecycle, @llmintel/mcp
- Stars
- 1
- Tools
- 5
- Downloads, 30 days
- 695
- Latest version
- 0.2.0
- Last commit
- Oct 20, 2026
- License
- MIT
What is LLMIntel Model Lifecycle MCP?
LLMIntel Model Lifecycle lets an AI agent check if LLM model IDs are deprecated or retired and find recommended replacements across major providers. It exposes 5 tools, such as check_model, list_retiring_models, suggest_replacement.
Summary generated from the project's README
About LLMIntel Model Lifecycle MCP server
LLMIntel Model Lifecycle helps developers and AI agents verify if specific large language model IDs are still active or have been retired. It provides a live lookup to prevent code from using deprecated models that no longer respond to API calls. The server aggregates data from major providers including OpenAI, Anthropic, Azure AI Foundry, AWS Bedrock, Google, and Cohere by parsing their official deprecation pages.
Users can run this server locally via npx or connect to a hosted HTTP endpoint. It requires no signup or API keys for standard use, though an optional key can increase rate limits. The system includes tools like check_model to verify a single ID, list_retiring_models to see upcoming expirations, and suggest_replacement to find recommended successors. It is designed to be used within MCP hosts like Cursor, Claude Desktop, or Claude Code.
What you can do with it
- 1Verify model safety in codeAn agent can scan a codebase to ensure all model identifiers are currently supported and not retired.
- 2Identify upcoming model expirationsA developer can request a list of models that are scheduled to stop working within a specific timeframe.
- 3Find suitable model replacementsWhen a model is deprecated, the agent can find the official successor recommended by the provider.
Written from the project's README. Every use case is checked against a quote from it.
How to install LLMIntel Model Lifecycle MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall LLMIntel Model Lifecycle MCP in Claude Code
$ claude mcp add --env 'LLMINTEL_API_KEY=<YOUR_LLMINTEL_API_KEY>' model-lifecycle -- npx -y @llmintel/mcpInstall LLMIntel Model Lifecycle MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"model-lifecycle": {
"command": "npx",
"args": [
"-y",
"@llmintel/mcp"
],
"env": {
"LLMINTEL_API_KEY": "<YOUR_LLMINTEL_API_KEY>"
}
}
}
}Install LLMIntel Model Lifecycle MCP in VS Code
.vscode/mcp.json
{
"servers": {
"model-lifecycle": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@llmintel/mcp"
],
"env": {
"LLMINTEL_API_KEY": "<YOUR_LLMINTEL_API_KEY>"
}
}
}
}Install LLMIntel Model Lifecycle MCP in VS Code CLI
$ code --add-mcp '{"name":"model-lifecycle","type":"stdio","command":"npx","args":["-y","@llmintel/mcp"],"env":{"LLMINTEL_API_KEY":"<YOUR_LLMINTEL_API_KEY>"}}'Install LLMIntel Model Lifecycle MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"model-lifecycle": {
"command": "npx",
"args": [
"-y",
"@llmintel/mcp"
],
"env": {
"LLMINTEL_API_KEY": "<YOUR_LLMINTEL_API_KEY>"
}
}
}
}Install LLMIntel Model Lifecycle MCP in Codex
$ codex mcp add model-lifecycle --env 'LLMINTEL_API_KEY=<YOUR_LLMINTEL_API_KEY>' -- npx -y @llmintel/mcpInstall LLMIntel Model Lifecycle MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.model-lifecycle] command = "npx" args = ["-y", "@llmintel/mcp"] [mcp_servers.model-lifecycle.env] LLMINTEL_API_KEY = "<YOUR_LLMINTEL_API_KEY>"
Install LLMIntel Model Lifecycle MCP in Gemini CLI
$ gemini mcp add -s user -e 'LLMINTEL_API_KEY=<YOUR_LLMINTEL_API_KEY>' model-lifecycle npx -- -y @llmintel/mcpInstall LLMIntel Model Lifecycle MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"model-lifecycle": {
"command": "npx",
"args": [
"-y",
"@llmintel/mcp"
],
"env": {
"LLMINTEL_API_KEY": "<YOUR_LLMINTEL_API_KEY>"
}
}
}
}LLMIntel Model Lifecycle MCP tools 5
Detected from the READMEcheck_modellist_retiring_modelssuggest_replacementsearch_modelsrecent_lifecycle_changes
| check_model | — | |
| list_retiring_models | — | |
| suggest_replacement | — | |
| search_models | — | |
| recent_lifecycle_changes | — |
Configuration
LLMINTEL_API_KEYSecretOptional. The catalog is public and needs no key; supplying one only raises the rate-limit budget.
LLMINTEL_BASE_URLOptional. Override the catalog origin (defaults to https://llmintel.ai). Useful for self-hosted or staging deployments.
| Name | Description | |
|---|---|---|
| LLMINTEL_API_KEY | Optional. The catalog is public and needs no key; supplying one only raises the rate-limit budget. | Secret |
| LLMINTEL_BASE_URL | Optional. Override the catalog origin (defaults to https://llmintel.ai). Useful for self-hosted or staging deployments. |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@llmintel/mcp
An MCP server that tells your coding agent whether a model id is safe to use.
LLMs are trained on a snapshot of the world and will confidently write gpt-4-32k into your code
long after it stops answering. This server gives the agent a live lookup for whether a model is
deprecated and when it stops working. It returns the replacement too. Answers are normalized across
OpenAI, Anthropic, Azure AI Foundry, AWS Bedrock, Google, and Cohere, and parsed from each
provider's own deprecation pages.
No API key, no signup. The catalog is public.
Install
Add it to any MCP host. The package runs straight from npm via npx.
Cursor
In .cursor/mcp.json:
{
"mcpServers": {
"llmintel": {
"command": "npx",
"args": ["-y", "@llmintel/mcp"]
}
}
}
Claude Code
claude mcp add llmintel -- npx -y @llmintel/mcp
Claude Desktop
Same shape as the Cursor block above, in claude_desktop_config.json.
Hosted endpoint (no install)
The same five tools are served over Streamable HTTP at https://llmintel.ai/v1/mcp. Hosts that take
a URL need no Node and no package:
{
"mcpServers": {
"llmintel": {
"url": "https://llmintel.ai/v1/mcp"
}
}
}
The endpoint is stateless and read-only. It answers from the same catalog the npm package queries.
Tools
| Tool | Returns |
|---|---|
check_model |
Whether one model id is safe to use: lifecycle state, the retirement deadline in days, the replacement, and the source link. |
list_retiring_models |
What breaks in the next 180 days (default; configurable up to 1095). Past-due models are listed first, then upcoming ones soonest-first. |
suggest_replacement |
The provider's own recommendation for what to move to. Falls back to same-provider active models when none was published. |
search_models |
Catalog search filtered by provider and lifecycle state. |
recent_lifecycle_changes |
The change feed across all providers, for questions like "what was deprecated this month". |
Example
You: Before we ship this, check the model ids in
src/agents/.
The agent calls check_model for each one and gets back:
DO NOT USE — this model is retired; API calls to it fail.
"claude-sonnet-4-20250514" resolves to the tracked model anthropic/claude-sonnet-4-20250514.
Model: claude-sonnet-4-20250514 (anthropic/claude-sonnet-4-20250514)
Provider: anthropic
Lifecycle state: retired — retired; calls fail
Deprecated: 2026-04-14 (105 days ago)
Retirement: 2026-06-15 (43 days ago)
The provider has not named a replacement. Use suggest_replacement for options.
Pricing/limits: $3/1M in · $15/1M out
Source: https://docs.anthropic.com/en/docs/about-claude/model-deprecations
Provider's own term: "Retired"
Deadlines are always given in days, because a model cannot reliably judge whether 2026-07-30 is
soon.
Design notes
A failed lookup is never a safety verdict. If the catalog is unreachable, the tool returns an MCP error and says so. An agent that read a network failure as "no deprecation found" would happily ship a retired model id. A model that simply isn't tracked gets the same treatment: it returns "not in the catalog, verify with the provider", never "OK".
Pass whatever string is literally in the code (gpt-4o, anthropic/claude-opus-4-1, azure/gpt-4o)
and it resolves to the canonical tracked model.
When the provider's own deprecation notice names a successor, that is what you get. Otherwise the fallback list of same-provider active models is labelled as candidates to evaluate, so an agent can tell the two apart.
Anything past its retirement date is broken now, so it gets its own heading instead of sitting in "retiring soon".
Configuration
Both variables are optional.
| Variable | Default | Purpose |
|---|---|---|
LLMINTEL_API_KEY |
none | Raises the rate-limit budget. The catalog itself is public, so you do not need this. |
LLMINTEL_BASE_URL |
https://llmintel.ai |
Point at a self-hosted or staging catalog. |
Anonymous callers get 30 requests/minute per IP, enough for interactive agent use.
Data provenance
Every record links to the provider page it was parsed from and preserves the provider's verbatim
lifecycle term (sourceTerm), so a normalization decision is always auditable. Changes go through a
human verification queue before publication. Collector freshness is public at
/v1/status.
The same data is available as a plain REST API, also without a key. See llmintel.ai/docs.
Where to find it
| Directory | Entry |
|---|---|
| Official MCP Registry | ai.llmintel/model-lifecycle |
| Glama | @hivemindunit/llmintel-mcp |
| Smithery | llmintel/model-lifecycle |
| npm | @llmintel/mcp |
Development
pnpm --filter @llmintel/mcp build
pnpm exec vitest run packages/mcp # protocol-level tests against a fake catalog
# Drive the built binary against a live catalog
pnpm --filter @llmintel/mcp smoke
LLMINTEL_BASE_URL=http://localhost:3000 pnpm --filter @llmintel/mcp smoke
License
MIT © LLMIntel
LLMIntel Model Lifecycle MCP questions
How do I add LLMIntel Model Lifecycle MCP to Claude Code?
Run claude mcp add --env 'LLMINTEL_API_KEY=<YOUR_LLMINTEL_API_KEY>' model-lifecycle -- npx -y @llmintel/mcp in your terminal. Add --scope user to make it available in every project.
How do I add LLMIntel Model Lifecycle MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does LLMIntel Model Lifecycle MCP provide?
It exposes 5 tools, including check_model, list_retiring_models, suggest_replacement, search_models, recent_lifecycle_changes.
Do I need an API key to use this server?
No, the catalog is public and you can use it without an API key or signup.
What happens if a model is not in the catalog?
The server will return a message stating the model is not in the catalog and to verify it with the provider, rather than assuming it is safe.
Can I use this without installing an npm package?
Yes, you can use a hosted HTTP endpoint if your MCP host supports URLs.
Is there a rate limit for anonymous users?
Yes, anonymous callers are limited to 30 requests per minute per IP.