mcp -endoflife

This MCP server provides a specialized toolset for querying and analyzing software end-of-life (EOL) data via the endoflife.date API. It exposes a suite of tools that let an AI assistant check EOL dates and support status, compare versions, scan for security CVEs, and retrieve comprehensive lifecycle details for multiple software products (including Python, Node.js, Ubuntu, and more). The server supports natural language queries and can return actionable guidance such as upgrade recommendations and security implications. Tools include check_version for current status, get_all_details for full lifecycle history, compare_versions for upgrade paths and urgency, check_cve for vulnerability insights, and list_products to browse available software with filters. Use the provided prompts to interact with the server and obtain structured responses that your AI can relay to users or chain into further actions.

Prerequisites:

• Node.js v18 or higher
• npm (comes with Node.js)
• Git

Installation steps:

1. Clone the repository:

git clone https://github.com/ducthinh993/mcp-server-endoflife
cd mcp-server-endoflife

2. Install dependencies:

npm install

3. Build the project (if applicable):

npm run build

4. Link the package globally (optional but convenient for Claude/Desktop integration):

npm link

5. Start the server (example):

npm run start

If you plan to use Claude Desktop integration, configure Claude with the provided MCP server entry (see Configuration section in the README).

Tips and considerations:

• The MCP server relies on the endoflife.date API; ensure you have network access and the API endpoint is reachable.
• When integrating with Claude Desktop, the config snippet often uses an absolute or built path to the server entry. Adapt the path as needed for your environment.
• If you encounter server-not-found errors, verify that the npm link (or your startup command) is running and that Claude Desktop is pointed at the correct MCP server identifier.
• Check for updates to the endoflife.date API and adjust parsing logic in your workflows if the API response shape changes.
• If running behind proxies or firewalls, ensure appropriate HTTP(S) access is allowed for the MCP server to fetch EOL and CVE data.