Overview
What is EOL MCP Server?
An MCP server that enables AI assistants like Claude to check software end-of-life (EOL) dates and support status using the endoflife.date API, providing real-time software lifecycle and security information.
How to use EOL MCP Server?
Install via cloning the repository, running npm install, npm run build, and npm link. Then configure Claude Desktop by adding an eol entry under mcpServers in its config JSON file, pointing to the built server path. Restart Claude Desktop to connect.
Key features of EOL MCP Server
- Real-time software end-of-life date validation
- Version support status and LTS checking
- Security vulnerability (CVE) analysis per version
- Version comparison with upgrade recommendations
- Natural language query processing for lifecycle questions
- Caches recent queries for quick reference
Use cases of EOL MCP Server
- Check if a specific software version (e.g., Python 3.8) is still supported
- Analyze security concerns and CVEs for a given version (e.g., Node.js 16)
- Compare multiple Ubuntu LTS releases to choose the best one
- Get upgrade urgency and recommended versions for outdated software
- Validate upgrade paths and compatibility between versions
FAQ from EOL MCP Server
What software products does EOL MCP Server support?
It supports a wide range of software products tracked by the endoflife.date API, including Python, Node.js, Ubuntu, Go, and many others. Use the list_products tool to browse available software.
What dependencies are required to run EOL MCP Server?
You need Node.js v18 or higher, the Claude Desktop app, Git, and an internet connection to access the endoflife.date API.
Does EOL MCP Server store or cache my data?
The README mentions it caches recent queries for quick reference, but no persistent storage beyond local caching is described.
What transports does EOL MCP Server use?
It uses standard I/O transport as an MCP server, communicating via JSON messages over stdin/stdout with the host application (Claude Desktop).
How do I troubleshoot connection issues?
Restart Claude Desktop completely and check its logs (e.g., tail -n 20 -f ~/Library/Logs/Claude/mcp*.log on macOS). Verify the npx path and config syntax in the claude_desktop_config.json file.
