endoflife.ai — Software Lifecycle Intelligence MCP Server

by endoflife-ai Your server? Claim it

answering

endoflife.ai — Software Lifecycle Intelligence is answering right now. Last checked 2 min ago. It exposes 10 tools. Last commit 5 Nov 2026.

EOL dates, risk scores, CISA KEV exposure, SBOM audits and edge-device EOS for 700+ products.

Uptime history 91 days of history · worst day 95%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

145 ms

Response time

average over 24h

Stars

last commit 5 Nov 2026

What changed 23

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

10 Nov 2 tool descriptions were rewritten check_sbom, scan_stack

10 Nov a tool changed version

5 Nov a tool changed version

31 Oct a tool changed version

21 Oct a tool description was rewritten list_products

11 Oct 2 tool descriptions were rewritten check_sbom, scan_stack

11 Oct a tool changed the parameters it asks for check_sbom

11 Oct a tool changed version

5 Sep a tool changed version2 times that day

5 Sep a tool description was rewritten check_eol

and 11 more, back to 3 September 2026

Nothing serious here today

Today is the operative word: we check endoflife.ai — Software Lifecycle Intelligence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://mcp.endoflife.ai

~/.codex/config.toml

[mcp_servers.endoflife-mcp]
url = "https://mcp.endoflife.ai"

.cursor/mcp.json

{
  "mcpServers": {
    "endoflife-mcp": {
      "url": "https://mcp.endoflife.ai"
    }
  }
}

.vscode/mcp.json

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

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

edge

get_edge_device_status

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?".

eol

check_eol

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.

kev

get_kev_exposure

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.

product

get_product_lifecycle

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".

products

list_products

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.

risk

get_risk_score

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.

sbom

check_sbom

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.

scan

scan_stack

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.

upcoming

get_upcoming_eol

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?".

upgrade

get_upgrade_path

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.endoflife.ai	streamable-http	answering	106 ms	2 min ago

Alternatives to endoflife.ai — Software Lifecycle Intelligence

same job, measured the same way

satoshidata — Bitcoin entity intelligence

by satoshidata

Bitcoin entity and risk-exposure evidence for AI agents; keyless MCP, no risk_check score/verdict.

44 tools answering

Endoflife Date MCP

by mrfentmen

endoflife.date: support windows and end of life dates for software releases - keyless.

339 installs/wk local only

Dev Facts Check

by openkrill

Software end-of-life dates, open-source licenses, browser support for web features and RFC facts.

8 tools answering

AfriResolve

by afriresolve

African intelligence infrastructure for AI apps, developers, and data products via MCP.

13 tools answering

Endoflife MCP

by mrfentmen

Check software end of life dates from endoflife.date. No key required.

100 installs/wk local only

TWZRD Agent Intelligence

by twzrd-intel

Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.

142 installs/wk 28 tools answering

TWZRD Agent Intelligence

by twzrd-sol

Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.

local only

Openplan

by vncsleal

Plan, track, and learn from software projects — three MCP tools for the AI agent lifecycle.

local only

endoflife.ai — Software Lifecycle Intelligence — questions

Answers built from our own checks of this server.

What can endoflife.ai — Software Lifecycle Intelligence do?

It exposes 10 tools, read directly from the server on our last check. Among them: check_eol, check_sbom, get_edge_device_status, get_kev_exposure, get_product_lifecycle, get_risk_score and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is endoflife.ai — Software Lifecycle Intelligence working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 145 ms. The bar chart above shows every period we have measured.

How do I connect endoflife.ai — Software Lifecycle Intelligence?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does endoflife.ai — Software Lifecycle Intelligence need an API key?

No. endoflife.ai — Software Lifecycle Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is endoflife.ai — Software Lifecycle Intelligence?

It answers our handshake in 145 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is endoflife.ai — Software Lifecycle Intelligence open source?

The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.endoflife.ai, which runs on its operator's own terms.