End-of-Life API

by ducthinh993

3 stars

Not rated

GitHub

About

Integrates with the endoflife.date API to provide software end-of-life status checks for dependency management, security auditing, and upgrade planning.

Details

Author: ducthinh993
Repository: ducthinh993/mcp-server-endoflife
GitHub stars: 3
License: MIT License
Categories: Developer Tools, API, Knowledge Base, Design, Workplace, AI, Search, Frontend, Infrastructure, Security

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below
Plugin Name End-of-Life API

Command (node, npx, python, etc.) npx
Arguments
- Argument 1 /path/to/eol-mcp-server/build/index.js
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/c",
                "npx",
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": true,
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/c",
                "npx",
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": true,
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/c",
                "npx",
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": true,
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/c",
                "npx",
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": true,
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/c",
                "npx",
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": true,
            "command": "cmd"
        }
    }
}

JSON

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

`check_version`

Get EOL dates and support status, check latest patch versions, verify LTS status, and validate support timeline.

`get_all_details`

Get comprehensive lifecycle details, view all version cycles, check support timeline, get validation results, and calculate remaining support days.

`compare_versions`

Compare current vs latest versions, get upgrade recommendations, check compatibility, assess upgrade urgency, and validate upgrade paths.

`check_cve`

Perform security vulnerability scanning, support status verification, security patch validation, and vendor support checking.

`list_products`

Browse available software, search with filters, verify product names, and get product details.

1. check_version
- Get EOL dates and support status
- Check latest patch versions
- Verify LTS status
- Validate support timeline

2. get_all_details (New!)
- Get comprehensive lifecycle details
- View all version cycles
- Check support timeline
- Get validation results
- Calculate remaining support days

3. compare_versions
- Compare current vs latest versions
- Get upgrade recommendations
- Check compatibility
- Assess upgrade urgency
- Validate upgrade paths

4. check_cve
- Security vulnerability scanning
- Support status verification
- Security patch validation
- Vendor support checking

5. list_products
- Browse available software
- Search with filters
- Verify product names
- Get product details

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "end-of-life api": {
            "cwd": "",
            "env": {},
            "args": [
                "/path/to/eol-mcp-server/build/index.js"
            ],
            "shell": false,
            "command": "npx"
        }
    }
}

Linux

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

Macos

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

Windows

{
    "cwd": "",
    "env": [],
    "args": [
        "/c",
        "npx",
        "/path/to/eol-mcp-server/build/index.js"
    ],
    "shell": true,
    "command": "cmd"
}

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.

- Checks software end-of-life dates and support status
- Scans for CVE vulnerabilities in software versions
- Provides version comparison and upgrade recommendations
- Supports natural language queries about software lifecycle
- Handles multiple software products (Python, Node.js, Ubuntu, etc.)
- Caches recent queries for quick reference

- Real-time EOL date validation
- Version support status checking
- Security vulnerability analysis
- Comprehensive version comparison
- Natural language query processing
- Detailed lifecycle validation

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

- Get comprehensive lifecycle details
- View all version cycles
- Check support timeline
- Get validation results
- Calculate remaining support days

- Compare current vs latest versions
- Get upgrade recommendations
- Check compatibility
- Assess upgrade urgency
- Validate upgrade paths

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

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

- Validate version support
- Check EOL dates
- Get security status

- Analyze version differences
- Get upgrade recommendations
- Check compatibility

- Security vulnerability analysis
- Support status check
- Patch verification

- Process natural language questions
- Get contextual responses
- Smart version detection

- Validate version recommendations
- Check support status
- Verify security implications

{ "current_date": "2024-02-20T00:00:00.000Z", "validations": { "current": { "version": "1.20", "eol_check": { "date": "2024-02-06", "valid": false, "days_remaining": -14, "message": "Version 1.20 EOL date 2024-02-06 is invalid, -14 days from now" }, "support": { "status": "not supported", "lts": "not LTS" } } }, "recommendation": { "needs_update": true, "urgency": "critical", "message": "Current version needs urgent upgrade - use a supported version" } }

{ "product": "go", "current_date": "2024-02-20T00:00:00.000Z", "cycles": [ { "cycle": "1.22", "releaseDate": "2024-02-06", "eol": "2025-02-06", "latest": "1.22.0", "validation": { "is_valid": true, "days_to_eol": 351, "is_supported": true, "message": "Version 1.22 EOL date 2025-02-06 is valid, +351 days from now" } } ] }

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.

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.

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.

- Node.js(v18 or higher)
- Claude Desktopinstalled
- Git installed

You can verify your Node.js installation by running:

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

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

Configure Claude Desktop to recognize the EOL MCP server:

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

code %APPDATA%\Claude\claude_desktop_config.json

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

- Completely quit Claude Desktop (not just close the window)
- Start Claude Desktop again
- Look for the 🔌 icon to verify the EOL server is connected

- Verify the npm link is correctly set up
- Check Claude Desktop configuration syntax
- Ensure Node.js is properly installed

- Check if endoflife.date API is accessible
- Verify the API response format hasn't changed
- Check network connectivity

- Restart Claude Desktop completely
- Check Claude Desktop logs:

# macOS tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

- Review theMCP Documentation
- Check the endoflife.date API Documentation
- Open an issue in the GitHub repository

- endoflife.datefor their comprehensive software lifecycle API
- Model Context Protocolfor the MCP specification
- Anthropicfor Claude Desktop

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.

A TypeScript MCP server to access Apifox API data via Stdio.

Provides API documentation from Apifox projects as a data source for AI programming tools that support MCP.

A tool to retrieve API interface information from YApi, with authentication configurable via environment variables.

Clix MCP Server for assisting Clix SDK/API integrations with semantic search across Clix docs and SDK source (iOS, Android, Flutter, React Native).

Fetches API information from Feishu OpenAPI for seamless integration and management within an IDE.

Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding

Provides educational content, model information, and read-only API interactions for Lerian developers.

Interact with an MCP registry to check health, list entries, and get server details.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

End-of-Life API

About

Details

Jump to

Setting up with Highlight

Setting up with Cursor

JSON

JSON

JSON

Setting up with Claude Desktop

JSON

JSON

JSON

Setting up with Windsurf

JSON

JSON

JSON

Setting up with Cline

JSON

JSON

JSON

Setting up with Goose

JSON

JSON

JSON

`check_version`

`get_all_details`

`compare_versions`

`check_cve`

`list_products`

Claude Desktop / Cursor

Linux

Macos

Windows

Install

About

Details

Jump to

Setting up with Highlight

check_version

get_all_details

compare_versions

check_cve

list_products

Claude Desktop / Cursor

Linux

Macos

Windows

Install

More like this

Aws Kb Retrieval Server

Memory

Sentry

Github

Git

GitLab

`check_version`

`get_all_details`

`compare_versions`

`check_cve`

`list_products`