Skip to content

endoflife.ai — Software Lifecycle Intelligence MCP server

io.github.endoflife-ai/endoflife-mcpendoflife-aistreamable-httpv1.4.1Scanned

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

10 tools: 3 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 3 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the endoflife.ai — Software Lifecycle Intelligence MCP server can do

The endoflife.ai — Software Lifecycle Intelligence MCP server is published by the GitHub account endoflife-ai. It has 10 tools. It can create or change data (3 tools: check_eol, scan_stack and check_sbom), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.4.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 3Claude Code: ask
  • check_eolCheck whether a specific version of a software product is end-of-life (EOL).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check end-of-life status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_sbomAudit a CycloneDX or SPDX JSON software bill of materials.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check an SBOM
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • scan_stackAudit a whole stack at once.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Scan a stack
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • get_edge_device_statusQuery 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 CI…No findings

    Why it is in this group

    • The name "get_edge_device_status" says "get": a word for reading.
    Description, as the server wrote it
    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?".

    Annotations the server declares

    • title: EOS Edge Device status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_kev_exposureThe 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…No findings

    Why it is in this group

    • The name "get_kev_exposure" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: CISA KEV exposure
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_product_lifecycleGet the full version history for one product: every tracked version/cycle with its release date, EOL date, support status, and EOL Risk Score.No findings

    Why it is in this group

    • The name "get_product_lifecycle" says "get": a word for reading.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • title: Full lifecycle table
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_risk_scoreGet 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).No findings

    Why it is in this group

    • The name "get_risk_score" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: EOL Risk Score
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_upcoming_eolWhat reaches end-of-life soon.No findings

    Why it is in this group

    • The name "get_upcoming_eol" says "get": a word for reading.
    Description, as the server wrote it
    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?".

    Annotations the server declares

    • title: Upcoming end-of-life calendar
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_upgrade_pathWhere 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 t…No findings

    Why it is in this group

    • The name "get_upgrade_path" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Upgrade path
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_productsList or search the 700+ products endoflife.ai tracks.No findings

    Why it is in this group

    • The name "list_products" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a product slug
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:04 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.endoflife.ai: tools/list returned 10 tools to an anonymous client, including check_eol (write), scan_stack (write), check_sbom (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.4.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__endoflife__get_risk_score",
      "mcp__endoflife__list_products",
      "mcp__endoflife__get_product_lifecycle",
      "mcp__endoflife__get_kev_exposure",
      "mcp__endoflife__get_upcoming_eol",
      "mcp__endoflife__get_edge_device_status",
      "mcp__endoflife__get_upgrade_path"
    ],
    "ask": [
      "mcp__endoflife__check_eol",
      "mcp__endoflife__scan_stack",
      "mcp__endoflife__check_sbom"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as endoflife. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.endoflife-ai/endoflife-mcp/verify?hash=e1766a3fda2f79028b775194179b0e9c9e0770320989e0233644e566753f8492" | jq -e '.changed == false'

Pinned hash e1766a3fda2f, from Nov 16, 2026, 13:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.endoflife-ai/endoflife-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.endoflife-ai/endoflife-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.endoflife-ai/endoflife-mcp.svg)](https://radar.anlyon.com/servers/io.github.endoflife-ai/endoflife-mcp)

Source: MCP Registry · repository. Synced Nov 3, 2026, 03:17 UTC.

endoflife.ai — Software Lifecycle Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the endoflife.ai — Software Lifecycle Intelligence MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the endoflife.ai — Software Lifecycle Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the endoflife.ai — Software Lifecycle Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the endoflife.ai — Software Lifecycle Intelligence MCP server have?

10 tools: 3 write, 7 read. check_eol, scan_stack, check_sbom, get_risk_score, list_products, get_product_lifecycle, get_kev_exposure, get_upcoming_eol and 2 more.

Does the endoflife.ai — Software Lifecycle Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the endoflife.ai — Software Lifecycle Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the endoflife.ai — Software Lifecycle Intelligence MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.