End-of-Life API MCP server

Integrates with the endoflife.date API to provide software end-of-life status checks for dependency management, security auditing, and upgrade planning.
Back to servers
Setup instructions
Provider
Duc Thinh
Release date
Jan 24, 2025
Language
TypeScript
Stats
2 stars

This MCP server provides real-time end-of-life (EOL) data for software products, helping AI assistants like Claude deliver accurate information about software support status, security vulnerabilities, and upgrade recommendations using the endoflife.date API.

Installation

Prerequisites

Before installation, ensure you have:

Verify your Node.js installation with:

node --version  # Should show v18.0.0 or higher

Setup Steps

  1. Clone the repository:
git clone https://github.com/ducthinh993/mcp-server-endoflife
cd mcp-server-endoflife
  1. Install dependencies:
npm install
  1. Build the project:
npm run build
  1. Create a global link:
npm link

Configuration

Setting Up Claude Desktop

Configure Claude Desktop to recognize the EOL MCP server:

For macOS:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

For Windows:

code %APPDATA%\Claude\claude_desktop_config.json

Add the EOL server configuration:

{
  "mcpServers": {
    "eol": {
      "command": "npx",
      "args": ["/path/to/eol-mcp-server/build/index.js"]
    }
  }
}

Activating the Server

  1. Completely quit Claude Desktop (not just close the window)
  2. Restart Claude Desktop
  3. Look for the 🔌 icon to verify the EOL server is connected

Using the EOL Server

Available Tools

The server provides several powerful tools:

check_version

  • Get EOL dates and support status
  • Check latest patch versions
  • Verify LTS status
  • Validate support timeline

get_all_details

  • Get comprehensive lifecycle details
  • View all version cycles
  • Check support timeline
  • Calculate remaining support days

compare_versions

  • Compare current vs latest versions
  • Get upgrade recommendations
  • Check compatibility
  • Assess upgrade urgency

check_cve

  • Security vulnerability scanning
  • Support status verification
  • Security patch validation
  • Vendor support checking

list_products

  • Browse available software
  • Search with filters
  • Verify product names
  • Get product details

Example Conversations

Basic Version Check

Human: Is Python 3.8 still good to use?
Claude: Let me check the status of Python 3.8.
[Uses check_version tool]
Based on the EOL data, Python 3.8:
- Security support ends: October 2024
- Current status: Security fixes only
Recommendation: Consider upgrading to Python 3.11 for new projects.

Security Analysis

Human: Any security concerns with Node.js 16?
Claude: I'll analyze the security status of Node.js 16.
[Uses check_version tool]
[Uses check_cve tool]
Found:
- Support Status: LTS until September 2023
- Critical CVEs: 2 in last 6 months
- CVSS Score Range: 7.5-9.8
Recommendation: Update to latest 16.x patch or consider Node.js 18 LTS.

Version Comparison

Human: Which Ubuntu version should I use?
Claude: I'll help you compare Ubuntu versions.
[Uses version-comparison prompt]
Analysis:
- 22.04 LTS: Supported until 2027, recommended for new deployments
- 20.04 LTS: Supported until 2025, stable and widely used
- 18.04 LTS: Approaching EOL, plan migration
Recommendation: Use 22.04 LTS for best long-term support.

Troubleshooting

Common Issues

  1. Server Not Found

    • Verify the npm link is correctly set up
    • Check Claude Desktop configuration syntax
    • Ensure Node.js is properly installed
  2. API Issues

    • Check if endoflife.date API is accessible
    • Verify the API response format hasn't changed
    • Check network connectivity
  3. Connection Issues

    • Restart Claude Desktop completely
    • Check Claude Desktop logs:
      # macOS
      tail -n 20 -f ~/Library/Logs/Claude/mcp*.log
      

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "eol" '{"command":"npx","args":["eol-mcp-server"]}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "eol": {
            "command": "npx",
            "args": [
                "eol-mcp-server"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "eol": {
            "command": "npx",
            "args": [
                "eol-mcp-server"
            ]
        }
    }
}

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later