EOL
- javascript
7
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"ducthinh993-mcp-server-endoflife": {
"command": "npx",
"args": [
"/path/to/eol-mcp-server/build/index.js"
]
}
}
}You can extend your AI assistant with an MCP server that checks software end-of-life dates, CVE status, and upgrade recommendations in real time. This server connects to external data sources to deliver accurate lifecycle and security context for your software stack, helping you make informed decisions quickly.
How to use
You access the EOL MCP server through an MCP client. Once configured, you can query current EOL dates, compare versions, scan for security issues, and retrieve comprehensive lifecycle details. Use natural language prompts or explicit tool names to guide your assistant to validate versions, check support status, and get upgrade recommendations.
Typical usage patterns include checking a single product for its EOL status, comparing your current version against the latest supported release, and analyzing security posture by running a CVE check. You can also ask for a full lifecycle view to understand version cycles and remaining support days.
How to install
Prerequisites you need before you begin are Node.js v18 or higher, Claude Desktop installed, and Git installed.
# Verify Node.js version
node --version
# Clone the MCP server repository
git clone https://github.com/ducthinh993/mcp-server-endoflife
cd mcp-server-endoflife
# Install dependencies
npm install
# Build the project
npm run build
# Create a global link to run the server locally
npm link
Additional setup and configuration
Configure your MCP client to recognize and connect to the EOL MCP server. The client configuration enables the server to be used within your AI workflow. The setup example shows how to register the EOL server as a local process started via an MCP command.
{
"mcpServers": {
"eol": {
"command": "npx",
"args": ["/path/to/eol-mcp-server/build/index.js"]
}
}
}
Troubleshooting
If you encounter issues, verify the MCP connection is established, ensure the data source API is reachable, and check the client logs for errors related to server discovery or command execution.
Common problems and quick checks include server not found, API access issues, and connection failures. Restart the client completely after configuration changes and review the logs for any startup errors.
Available tools
check_version
Fetches EOL dates and support status for a given product, including latest patch versions and LTS status.
get_all_details
Retrieves comprehensive lifecycle details for a product, including all version cycles, support timelines, and remaining days.
compare_versions
Compares the current version with the latest supported version, provides upgrade recommendations, checks compatibility, and validates upgrade paths.
check_cve
Performs security vulnerability analysis for a product version, verifies support status, and checks for available patches.
list_products
Lists available software products, supports filters, and provides product details.