EndOfLife MCP Server
Related Servers
Alternatives to EndOfLife MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to check software end-of-life dates and support status using the endoflife.date API, providing accurate information on software lifecycle, security status, and upgrade recommendations in real-time.58MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying software product release and support timelines, including EOL dates, active-support end, latest patch, and LTS status for products or specific versions.42 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides product lifecycle, release cycle, and End of Life (EOL) date information from endoflife.date.-

endoflife-mcpofficial
AlicenseAqualityAmaintenanceSoftware end-of-life intelligence for AI agents: EOL dates, support timelines and 0-100 upgrade risk scores for 480+ products. Check whether a version is still supported, score its risk, or audit an entire stack.58 npmMIT- AlicenseAqualityBmaintenanceEnables checking project files like Dockerfile, .nvmrc, and CI workflows to determine whether pinned runtime, database, and OS versions are still supported, providing end-of-life dates, latest patches, and upgrade targets for 470+ products.3MIT
- FlicenseNot gradedqualityCmaintenanceEnables querying AI model lifecycle and deprecation data across OpenAI, Anthropic, Google Gemini, and Amazon Bedrock, including model status, sunset dates, and recommended replacements via MCP tools.-
TDQS
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.