Deprecation MCP server

deprecation-mcp

A free, open MCP server for checking whether a vendor API or SDK is active, deprecated, or sunset — so an agent doing upgrade/maintenance work can check before it breaks, instead of after.

API/SDK deprecations are scattered across changelog pages, RSS feeds (if you're lucky), and Sunset/Deprecation HTTP headers (if the vendor bothers implementing RFC 8594). This server puts a curated, hand-verified answer behind one tool call.

No payment gating, no metering, no billing code of any kind — this is a plain open MCP server.

What it exposes

One tool, check_deprecation:

check_deprecation(provider: string, target: string) -> {
  status: "active" | "deprecated" | "sunset" | "unknown",
  deprecated_on: string | null,
  sunset_on: string | null,
  replacement: string | null,
  migration_url: string | null,
  source_url: string,
  last_verified_at: string
}

status: "unknown" (with a blank source_url) is returned for any provider/target not in the curated dataset below — it means "not tracked", not "confirmed active."

Curated dataset

Ten provider APIs/SDKs, each checked against the vendor's own published page (sourceurl) on the date in lastverified_at. Data lives in data/deprecations.json.

Lookups are case-insensitive and also match each record's aliases (e.g. aws/aws-sdk resolves to aws-sdk-js-v2).

Run it

npm install
npm run build
npm start        # starts the stdio MCP server

Add to an MCP client

Claude Code (.mcp.json in your project, or claude mcp add):

{
  "mcpServers": {
    "deprecation": {
      "command": "node",
      "args": ["/absolute/path/to/deprecation-mcp/dist/index.js"]
    }
  }
}

Any other stdio-based MCP client config follows the same shape: run node dist/index.js as the server command.

Worked example

Once connected, an agent calls:

{
  "name": "check_deprecation",
  "arguments": { "provider": "aws", "target": "aws-sdk-js-v2" }
}

and gets back:

{
  "status": "sunset",
  "deprecated_on": "2024-09-08",
  "sunset_on": "2025-09-08",
  "replacement": "AWS SDK for JavaScript v3",
  "migration_url": "https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/migrating-to-v3.html",
  "source_url": "https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-javascript-v2/",
  "last_verified_at": "2026-08-08"
}

Tests

npm test   # builds, then runs node:test against the lookup logic

Updating the dataset

Edit data/deprecations.json directly — no build step or scraper needed, it's read at server startup. Each record needs a real sourceurl you actually checked and an accurate lastverifiedat. When you re-verify a record, recompute its contenthash too (see below).

Drift detection

Shortened. The full README is on GitHub.