check_cve
Scan for known security vulnerabilities and support status
LABSCO SUMMARY
Turns "is this old?" into a date and a number of days.
The useful output is not the EOL date on its own but the days remaining alongside the support status and LTS flag — that is what separates a version to schedule an upgrade for from one to fix this week. get_all_details is worth reaching for when you are choosing a target rather than checking a current version, because it returns every cycle with its own timeline in one call instead of one query per candidate.
What it is
An MCP server over endoflife.date, the community-maintained record of software lifecycle dates. It answers the question behind most dependency arguments — is this version still supported, and how urgently does it need to move — with dates rather than impressions.
What you get
- A version's end-of-life date, current support status, latest patch release and whether it is an LTS line —
check_version - Every release cycle for a product with release and EOL dates, support status and days remaining on each —
get_all_details - Your current version compared against the latest, with an upgrade recommendation and an urgency assessment —
compare_versions - Known vulnerabilities checked for a version alongside whether it is still receiving security patches —
check_cve - The products endoflife.date covers, browsable and searchable, so you can confirm the name before querying it —
list_products - Prompts for the questions that need shaping rather than a lookup:
check_software_status,compare_versions,analyze_security,natural_language_queryandvalidate_version
Requirements
No account and no key — endoflife.date is a public API. Node.js v18 or higher. The npm package name is eol-mcp-server (0.1.0); install from a clone with npm install, npm run build and npm link, then point your client at the built index.js.
Setup effort
One command — npx -y github:ducthinh993/mcp-server-endoflife
USE CASES
01
Deciding whether a runtime needs upgrading now
Check the version's support status and EOL date, then compare it against the latest release to get an urgency reading rather than a gut feeling.
02
Choosing which version to standardise on
Pull every cycle for the product with its dates and remaining support days, and pick the one whose timeline suits the project.
03
Answering a security question about an old dependency
Check known vulnerabilities for the version alongside whether it is still receiving patches — an unpatched CVE on an unsupported line is a different answer from one on a supported one.
04
Auditing a stack you inherited
Confirm each product's name against the catalogue, then check the versions in use one by one to find which are already past end of life.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_version
Check EOL status and support information for software versions
compare_versions
Compare versions and get detailed upgrade analysis
get_all_details
Get comprehensive lifecycle details for all versions of a product
list_products
Browse or search available software products
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-server-endoflife": {
"command": "npx",
"args": [
"-y",
"github:ducthinh993/mcp-server-endoflife"
]
}
}
}npx
TERMINAL
npx -y github:ducthinh993/mcp-server-endoflife
