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.
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.
- 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_query` and `validate_version`
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`.
One command — npx -y github:ducthinh993/mcp-server-endoflife