EOL

You can run an MCP server that lets AI assistants query end-of-life dates, support status, and CVE information for software. This enables real-time lifecycle insights while keeping users in control of data sources and actions.

How to use

Use the MCP client to connect to the EOL MCP server and perform practical checks like validating current software versions, comparing against latest releases, and scanning for security vulnerabilities. You can ask natural language questions such as “What is the EOL status of Python 3.11?” or request upgrade recommendations for a given stack. The server processes these requests through its tools and returns actionable results that help you plan secure, up-to-date deployments.

How to install

Prerequisites you need before installing:

• Node.js 18 or higher
• Git
• npm installed

Follow these concrete steps to set up the EOL MCP server locally:

# Verify Node.js version
node --version

# Clone the project
git clone https://github.com/ducthinh993/mcp-server-endoflife
cd mcp-server-endoflife

# Install dependencies
npm install

# Build the project
npm run build

# Link the project globally (optional for local development)
npm link

Configuration

Configure the MCP client (Claude Desktop) to recognize the EOL MCP server. The client is configured via a JSON file that maps an MCP server name to a runtime command and its arguments. Use the following configuration for the EOL server, which runs through npx and points to the built entry point.

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

Restart and verify connection

After updating the configuration, fully quit the client and start it again to apply changes. Look for the connected status indicator to confirm the EOL server is connected.

Troubleshooting

If you encounter issues, try the following steps to diagnose common problems. Check that the server process is reachable by the client, verify the configuration syntax, and ensure the local environment has network access to any external APIs used by the server.

Notes and considerations

The server relies on external data sources for lifecycle information. Ensure you have network access to end-of-life data APIs and be prepared for data source changes that may affect results.

Prompts and usage patterns

Use prompts to drive specific checks such as validating a version’s EOL status, comparing versions, analyzing CVEs, and performing natural language queries about software lifecycles. The server provides structured responses with dates, statuses, and recommended actions to help you make informed decisions.

Example conversations

Basic Version Check you can guide the assistant to perform checks on a given software version and interpret the results to decide if an upgrade is advisable.

Supported tools and prompts

The following tools and prompts are exposed by the server to enable lifecycle checks, comparisons, and security analyses. Access these through your MCP client to perform concrete actions and get detailed results.

Security and privacy

Treat external data carefully and review any results for accuracy. If you rely on third-party APIs for vulnerability data, consider validating findings with additional sources in your workflow.

Available tools

check_version

Get EOL dates and support status for a given product, with latest patch versions and LTS status.

get_all_details

Fetch comprehensive lifecycle details, version cycles, support timelines, validation results, and remaining days of support.

compare_versions

Compare current versus latest versions, provide upgrade recommendations, check compatibility, and validate upgrade paths.

check_cve

Scan security vulnerabilities, verify support status, and check for available patches.

list_products

Browse available software, filter by criteria, verify product names, and retrieve product details.