MCP.so
Sign In

endoflife.ai MCP ServerVerifiedFeatured

@endoflife.ai

Basic information

Transport

Streamable HTTP

Authentication

None

Last updated

Category

Developer Tools

Author

endoflife.ai

Submitted by

endoflife-ai

About endoflife.ai MCP Server

Free MCP server for software end-of-life intelligence: EOL dates, support status, and the 0-100 EOL Risk Score across 480+ tracked products. Agents can check a single version, pull a product's full lifecycle schedule, or audit an entire dependency stack in one call. Dates are backed by a vendor-verified accuracy layer - see https://endoflife.ai/accuracy

Connection details

https://mcp.endoflife.ai

Setup

claude mcp add endoflife --transport http https://mcp.endoflife.ai

endoflife.ai MCP Server tools

10

Check whether a specific version of a software product is end-of-life (EOL). Returns lifecycle status, the EOL date, days remaining or days past EOL, the latest release, and eol_date_source (where the date comes from: vendor-override, vendor-fetched, vendor-verified, custom, upstream, or discrepancy) with its source URL. Use this for "is X version Y still supported?" questions.

Get the proprietary EOL Risk Score (0-100) for a product version, with the four-factor breakdown (EOL recency, attack surface, CISA KEV exposure, extended support). Omit "version" to score the product's highest-risk (most recently end-of-lifed) release. Use this to quantify how dangerous it is to keep running something.

Audit a whole stack at once. Provide a list of products (optionally with versions) — e.g. parsed from a package.json or Dockerfile — and get an EOL Risk Score for each, so you can see what is unsupported and dangerous in one call. For CycloneDX or SPDX documents use check_sbom instead. Without an API key up to 5 items are checked per call (a key raises the limit); items beyond it are listed as not checked, with a note.

List or search the 700+ products endoflife.ai tracks. Pass an optional "query" substring to find the canonical slug for a product before calling the other tools (e.g. "postgres" → "postgresql"). Returns matching product slugs.

Get the full version history for one product: every tracked version/cycle with its release date, EOL date, support status, and EOL Risk Score. Use for "give me the whole EOL schedule for X".

The exploited-vulnerability record for a product: every CVE CISA lists against it in the Known Exploited Vulnerabilities catalog, with the date added, the federal due date and CISA's required-action text verbatim (the "discontinue use" entries are the ones that matter for end-of-life versions), plus any entries from endoflife.ai's Exploited & Unpatchable feed (exploited CVEs whose affected versions will never receive a fix). Pass an optional version to include its support status alongside.

What reaches end-of-life soon. Returns every tracked version whose EOL date falls within the next N days (default 90), optionally limited to a list of products, sorted by date. Also lists versions that went EOL within the last "recent_past_days" days when set. Use for "what in our stack expires this quarter?".

Query the EOS Edge Device Intelligence feed — firewalls, VPN gateways and appliances, ADCs, router and switch operating systems — with end-of-support status in the vocabulary of CISA BOD 26-02 (eos, within-12-months, scheduled, no-date-announced). Filter by platform or vendor name, by status, or by model/line. Each platform carries its KEV summary, vendor-stated successor and provenance. Use for "which of our edge devices are past support or expire within 12 months?".

Where to move a product version: the current version's support status and score, the supported releases with the longest remaining support, endoflife.ai's recommended target, and the vendor's stated successor where one is published (edge appliances). Use after check_eol says a version is EOL.

Audit a CycloneDX or SPDX JSON software bill of materials. Components are mapped to tracked products and scored for EOL risk; unmatched components are listed honestly rather than guessed. Pass the SBOM as a JSON string or object. Versions resolve to their release family (python 3.12, php 7.4, ubuntu 20.04). Without an API key up to 5 matched components are scored per call (a key raises the limit); larger SBOMs return the scored subset plus a note of how many were not checked.

Overview

What is endoflife.ai MCP?

A free, no-auth remote MCP server that gives AI agents live software lifecycle intelligence: end-of-life dates, support status, and the 0–100 EOL Risk Score™ for 480+ tracked products — operating systems, runtimes, databases, frameworks, and enterprise software.

Tools

  • check_eol — EOL status and dates for a specific product version
  • get_risk_score — the 0–100 EOL Risk Score with factor breakdown (recency, attack surface, CISA KEV exposure, extended support)
  • scan_stack — audit an entire dependency list in one call
  • list_products — browse the 480+ product catalog
  • get_product_lifecycle — a product's full version/lifecycle schedule

Why this data

  • Vendor-verified accuracy layer: flagship products are cross-checked against official vendor lifecycle documentation, with published corrections and full provenance — see endoflife.ai/accuracy and the machine-readable verification.json
  • Built on the open-source endoflife.date dataset plus vendor lifecycle pages, refreshed at every build
  • CISA KEV exposure name-verified against the live catalog

Quick start

{
  "mcpServers": {
    "endoflife": {
      "type": "http",
      "url": "https://mcp.endoflife.ai"
    }
  }
}

No API key required. An optional X-API-Key header unlocks higher rate limits (endoflife.ai/api).

Links

Frequently asked questions

1

What is the endoflife.ai remote MCP server?

The endoflife.ai remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.endoflife.ai, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the endoflife.ai MCP server?

Add the endpoint https://mcp.endoflife.ai to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the endoflife.ai MCP server require authentication?

No. endoflife.ai's MCP server does not require authentication — you can connect directly with the endpoint URL.

4

Which transport does the endoflife.ai MCP server use?

endoflife.ai exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments