Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@EndOfLife MCP Server When does Ubuntu 22.04 reach end of life?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP (Model Context Protocol) server that provides access to the endoflife.date API for querying end-of-life and support information for various software products.
The server provides the following tools:
list_products - Get a list of all products tracked by endoflife.date
get_product - Get detailed information about a specific product
get_product_release - Get information about a specific product release
list_categories - Get a list of all product categories
get_category_products - Get products in a specific category
list_tags - Get a list of all product tags
get_tag_products - Get products with a specific tag
Related MCP server: Endoflife MCP Server
npm install
npm run buildThe server can be used with any MCP-compatible client. Configure your client to use this server:
{
"mcpServers": {
"endoflife": {
"command": "node",
"args": ["/path/to/endoflife-mcp/dist/index.js"]
}
}
}npm run dev # Run in development mode with watch
npm run build # Build the project
npm start # Run the built serverThis server interfaces with the endoflife.date API v1, providing structured access to end-of-life dataset for thousands of software products.
MIT
Find all products within a specific category. Useful for comparative analysis or when users ask broad questions like 'What databases are tracked?' or 'Show me all the operating systems.' Much more focused than browsing all products.
Inputs: category (required).
Get comprehensive end-of-life information for a specific software product. Returns all release cycles, support dates, and EOL status. Perfect for answering questions like 'When does Python 3.8 reach end-of-life?' or 'What Ubuntu versions are still supported?'
Inputs: product (required).
Get detailed information about a specific version/release of a product. Use this when you need precise details about one particular version, such as exact end-of-life dates, support status, or the latest patch version available.
Inputs: product (required), release (required).
Find all products that share a common tag. Useful for discovering related technologies or when users want to see all products from a specific vendor or with particular characteristics.
Inputs: tag (required).
Discover how products are organized by category. Returns categories like 'os' (operating systems), 'lang' (programming languages), 'db' (databases), 'server-app' (server applications), etc. Use this to understand the taxonomy or to help users explore related products.
Inputs: no named parameters.
Browse all software products tracked for end-of-life information. Use this as your starting point to discover what products are available, or when you need to help users find software they're asking about. Returns product names, descriptions, and basic metadata.
Inputs: full.
Explore products by tags/labels that describe their characteristics. Tags provide a different organizational system than categories, often describing technical attributes, company associations, or use cases.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Every tool has a clearly distinct purpose with no ambiguity: get_category_products filters by category, get_product retrieves detailed EOL info for a specific product, get_product_release focuses on a single version, get_tag_products filters by tags, list_categories shows available categories, list_products lists all products, and list_tags shows all tags. The descriptions explicitly differentiate their scopes, making misselection unlikely.
All tools follow a consistent verb_noun pattern using snake_case: get_*, list_*. The verbs 'get' and 'list' are used predictably—'get' for retrieving specific items and 'list' for browsing collections. There are no deviations in naming conventions across the set.
With 7 tools, this server is well-scoped for its purpose of querying end-of-life information. Each tool earns its place by covering distinct aspects of the domain: browsing (list_*), filtering (get_* by category/tag), and detailed retrieval (get_product, get_product_release). The count is neither too thin nor overwhelming.
The tool set provides complete coverage for the EOL domain, enabling agents to explore categories and tags, browse all products, filter by category or tag, retrieve detailed product info, and drill down to specific releases. There are no obvious gaps; agents can navigate from broad discovery to precise queries without dead ends.
Release, support and end-of-life dates for about 490 languages, OSes, databases and frameworks
Latest versions, LTS windows, and EOL dates for 300+ products. Fresh ground truth for stale models.
Software end-of-life dates, open-source licenses, browser support for web features and RFC facts.
EOL dates, risk scores, CISA KEV exposure, SBOM audits and edge-device EOS for 700+ products.
