A Model Context Protocol server that checks software end-of-life status using endoflife.date API
If you want an AI assistant working directly with Endoflife, the endoflife mcp server is the bridge. A Model Context Protocol server that checks software end-of-life status using endoflife.date API.
A Model Context Protocol (MCP) server that enables AI assistants like Claude to check software end-of-life (EOL) dates and support status using the endoflife.date API. This helps AI models provide accurate information about software lifecycle and security status in real-time.
The Model Context Protocol (MCP) is a system that lets AI apps, like Claude Desktop, connect to external tools and data sources. It provides a standardized way for AI assistants to work with local services and APIs while keeping the user in control.
Once connected, the assistant can call these 2 tools directly:
Tools — 1. check_version - Get EOL dates and support status - Check latest patch versions - Verify LTS status - Validate support timelinePrompts — 1. check_software_status - Validate version support - Check EOL dates - Get security statusSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Before you begin, ensure you have: - Node.js (v18 or higher) - Claude Desktop installed - Git installed You can verify your Node.js installation by running:
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Endoflife sits in that group, and the shape of its toolset — Tools, Prompts — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Tools | 1. check_version - Get EOL dates and support status - Check latest patch versions - Verify LTS status - Validate support timeline |
| Prompts | 1. check_software_status - Validate version support - Check EOL dates - Get security status |
{
"mcpServers": {
"eol": {
"command": "npx",
"args": ["/path/to/eol-mcp-server/build/index.js"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Before you begin, ensure you have: - Node.js (v18 or higher) - Claude Desktop installed - Git installed You can verify your Node.js installation by running:
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.