SERVER

LLMIntel Model Lifecycle

Rank #74,016

ai.llmintel/model-lifecycle

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

1 version

1 GitHub stars

by hivemindunit (3 servers)View repository ↗

Listed & last published

Jul 28, 2026

PURPOSE

What you can do with LLMIntel Model Lifecycle

LLMIntel Model Lifecycle is a Model Context Protocol (MCP) server published by hivemindunit. It ranks #74,016 of 147,587 active servers on MCP Toplist, and its repository has 1 GitHub stars. LLMIntel Model Lifecycle is listed on Official MCP, with 1 tracked version. It was first listed on Jul 28, 2026 and most recently updated on Jul 28, 2026.

Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.

CAPABILITIES AND LIMITATIONS

What LLMIntel Model Lifecycle can and cannot do

MCP Toplist connected to the public endpoint on Oct 10, 2026 and it listed 5 tools. Tool names are not stored, so what they do is not catalogued here.

Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.

REQUIREMENTS

What you need before using LLMIntel Model Lifecycle

VerifiedNo credentialsNo credentials declared

The registry listing declares no required environment variables or authentication. This is declared metadata, not a verified install — the repository README is the authority.

Verified by MCP Toplist on Oct 10, 2026: the public endpoint completed the MCP handshake and listed 5 tools without credentials.

Declared by the Official MCP Registry, last synced Oct 17, 2026. Not independently verified by MCP Toplist.

Declared in the registry install config

LLMINTEL_API_KEY · optional
LLMINTEL_BASE_URL · optional

Hosted endpoint declared as public.

INSTALLATION AND FIRST TASK

Connect LLMIntel Model Lifecycle and confirm it works

Remote · HTTP

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

npm package

claude mcp add model-lifecycle -e "LLMINTEL_API_KEY=<your LLMINTEL_API_KEY>" -e "LLMINTEL_BASE_URL=<your LLMINTEL_BASE_URL>" -- npx -y @llmintel/mcp

Replace each placeholder with your own value before saving.

Remote · HTTP

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

Add to ~/.codex/config.toml.

npm package

[mcp_servers.model-lifecycle]
command = "npx"
args = ["-y", "@llmintel/mcp"]

[mcp_servers.model-lifecycle.env]
LLMINTEL_API_KEY = "<your LLMINTEL_API_KEY>"
LLMINTEL_BASE_URL = "<your LLMINTEL_BASE_URL>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

Remote · HTTP

https://llmintel.ai/v1/mcp

Settings → Connectors → “Add custom connector”, then paste this URL.

npm package

{
  "mcpServers": {
    "model-lifecycle": {
      "command": "npx",
      "args": [
        "-y",
        "@llmintel/mcp"
      ],
      "env": {
        "LLMINTEL_API_KEY": "<your LLMINTEL_API_KEY>",
        "LLMINTEL_BASE_URL": "<your LLMINTEL_BASE_URL>"
      }
    }
  }
}

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

Remote · HTTP

{
  "mcpServers": {
    "model-lifecycle": {
      "url": "https://llmintel.ai/v1/mcp"
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).

npm package

{
  "mcpServers": {
    "model-lifecycle": {
      "command": "npx",
      "args": [
        "-y",
        "@llmintel/mcp"
      ],
      "env": {
        "LLMINTEL_API_KEY": "<your LLMINTEL_API_KEY>",
        "LLMINTEL_BASE_URL": "<your LLMINTEL_BASE_URL>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

Remote · HTTP

{
  "servers": {
    "model-lifecycle": {
      "type": "http",
      "url": "https://llmintel.ai/v1/mcp"
    }
  }
}

Save as .vscode/mcp.json in your workspace.

npm package

{
  "servers": {
    "model-lifecycle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@llmintel/mcp"
      ],
      "env": {
        "LLMINTEL_API_KEY": "<your LLMINTEL_API_KEY>",
        "LLMINTEL_BASE_URL": "<your LLMINTEL_BASE_URL>"
      }
    }
  }
}

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

Remote · HTTP

{
  "mcpServers": {
    "model-lifecycle": {
      "serverUrl": "https://llmintel.ai/v1/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

npm package

{
  "mcpServers": {
    "model-lifecycle": {
      "command": "npx",
      "args": [
        "-y",
        "@llmintel/mcp"
      ],
      "env": {
        "LLMINTEL_API_KEY": "<your LLMINTEL_API_KEY>",
        "LLMINTEL_BASE_URL": "<your LLMINTEL_BASE_URL>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

Remote · HTTP

{
  "mcpServers": {
    "model-lifecycle": {
      "url": "https://llmintel.ai/v1/mcp"
    }
  }
}

npm package

{
  "mcpServers": {
    "model-lifecycle": {
      "command": "npx",
      "args": [
        "-y",
        "@llmintel/mcp"
      ],
      "env": {
        "LLMINTEL_API_KEY": "<your LLMINTEL_API_KEY>",
        "LLMINTEL_BASE_URL": "<your LLMINTEL_BASE_URL>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

First successful task

After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.

MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed: Jul 28, 2026
Latest version published: Jul 28, 2026
Version history: 1 version tracked (below)
Requirements evidence: Verified by MCP Toplist on Oct 10, 2026: the public endpoint completed the MCP handshake and listed 5 tools without credentials.
Profile checked: Not yet — purpose, capabilities and requirements above come from registry data only
Ranking data as of: Jul 28, 2026

Registry sightings

Official MCP ↗listed since Jul 28, 2026 · still listed

Do you maintain LLMIntel Model Lifecycle? to correct or enrich this profile.

VERSIONS

Available versions (1)

Version	Published
0.2.0	Jul 28, 2026

STANDING

#74,016of 147,587 active servers

Ranks ahead of 73,571 of 147,587 servers on MCP Toplist.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/ai.llmintel%2Fmodel-lifecycle.svg)](https://mcptoplist.com/server/ai.llmintel%2Fmodel-lifecycle)

HTML

<a href="https://mcptoplist.com/server/ai.llmintel%2Fmodel-lifecycle"><img src="https://mcptoplist.com/badge/ai.llmintel%2Fmodel-lifecycle.svg" alt="MCP Toplist: #74,016 of 147,587" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Who maintains LLMIntel Model Lifecycle?: LLMIntel Model Lifecycle is maintained by hivemindunit, which publishes 3 MCP servers (2 total versions) tracked on MCP Toplist.
Is LLMIntel Model Lifecycle listed on the Official MCP Registry?: Yes — LLMIntel Model Lifecycle is listed on the Official MCP Registry.
How many versions does LLMIntel Model Lifecycle have?: MCP Toplist tracks 1 version of LLMIntel Model Lifecycle, most recently published on Jul 28, 2026.
Where can I find the source code for LLMIntel Model Lifecycle?: The source code for LLMIntel Model Lifecycle is hosted at github.com/hivemindunit/llmintel-mcp.

Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers