mcpField
A
ai-model-lifecycle-index

ai-model-lifecycle-index

Remote
data.oscar-lopez.comAI & Agents0Updated 6w ago
RepositoryVisit website

About ai-model-lifecycle-index

ai-model-lifecycle-index tracks model status, sunset dates, and migration targets across OpenAI, Anthropic, Google Gemini, and Amazon Bedrock, with official source citations. It is intended for agents checking at runtime whether a model remains callable.

Key features

  1. 01Cross-vendor model status lookup
  2. 02Release and sunset dates
  3. 03Provider-recommended replacements
  4. 04Upcoming deprecation lookup
  5. 05Models grouped by provider
  6. 06Full lifecycle data export

Use cases

  1. 01Check model availability before a call
  2. 02Plan migration from a retiring model
  3. 03Monitor upcoming shutdown dates
  4. 04Verify official lifecycle sources

MCP support

It provides an MCP server with tools for querying an individual model, checking whether it is live, listing upcoming deprecations, and exporting lifecycle data.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://lifecycle.oscar-lopez.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

4
ParameterTypeRequiredDescription
model_idstringYescanonical model id, e.g. 'gpt-4-32k', 'claude-3-opus-20240229', 'gemini-2.0-flash'

Details

From the project README

AI Model Lifecycle & Deprecation Index

A source-cited, cross-vendor record of AI model lifecycle — is a model still live, when does it sunset, and what's the migration target — across OpenAI, Anthropic, Google (Gemini), and Amazon Bedrock. Every date is transcribed from the provider's own official deprecation/lifecycle page and carries that source URL. Built for agents that need to know, at runtime, whether the model they're about to call still exists.

Coverage

71 models across 4 providers (active / preview / deprecated / retired), with status, release / deprecation / shutdown dates, and provider-recommended replacements. Verified 2026-09-08.

REST endpoints (free)

  • GET /v1/lifecycle/model?id=ID — one model: status, dates, days-to-shutdown, replacement, source
  • GET /v1/lifecycle/deprecations?within_days=90 — models shutting down within N days
  • GET /v1/lifecycle/provider?provider=openai|anthropic|google|aws-bedrock — a provider's models
  • GET /v1/lifecycle/stats — counts by provider/status + next shutdown
  • GET /v1/lifecycle/all — full export (free during the public preview; metered via x402 when live)

MCP tools

Endpoint: https://lifecycle.oscar-lopez.com/mcp

  • model_lifecycle — full lifecycle of one model (free)
  • is_model_live — is a model still callable, with its sunset date (free)
  • upcoming_deprecations — models sunsetting within N days across all providers (free)
  • get_model_lifecycle_all — full export (free during preview)

Discovery

/.well-known/agent-card.json (A2A), /.well-known/x402, /openapi.json

How it's built

Cloudflare Worker + D1. The index is derived live from a models table; days-until-shutdown is computed at request time. Values come from official provider pages only; fields a provider doesn't publish are left blank rather than inferred. A model's lifecycle on a hosting platform (e.g. Amazon Bedrock) can differ from the model-maker's own API — each row records which surface it describes.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.