LLMIntel Model Lifecycle
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLMINTEL_API_KEY | No | Raises the rate-limit budget. The catalog itself is public, so you do not need this. | |
| LLMINTEL_BASE_URL | No | Point at a self-hosted or staging catalog. | https://llmintel.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_modelA | 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. |
| list_retiring_modelsA | List tracked models scheduled to retire within a time window, soonest first. Use this to audit a codebase or plan migration work. |
| suggest_replacementA | 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. |
| search_modelsA | List tracked models, optionally filtered by provider and lifecycle state. Use this to discover what is currently available from a provider. |
| recent_lifecycle_changesA | Lifecycle state changes across all tracked providers, newest first. Use this to answer 'what model deprecations happened recently?'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: recent changes, model check, retiring list, replacement suggestion, and filtered search. No overlap or confusion.
Four tools follow verb_noun snake_case pattern (check_model, list_retiring_models, suggest_replacement, search_models), but recent_lifecycle_changes uses an adjective_noun pattern, creating a minor inconsistency.
Five tools are well-suited for a model lifecycle server, covering essential queries without being excessive or sparse.
The tool surface covers key lifecycle needs: checking status, listing retiring models, suggesting replacements, viewing recent changes, and search. No obvious gaps for a read-only information server.