eol-check-mcp
Related Servers
Alternatives to eol-check-mcp
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
- 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.31MIT

endoflife-mcpofficial
AlicenseAqualityBmaintenanceSoftware 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.519 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables checking whether software packages are deprecated, archived, stale, active, or unknown with supporting evidence, auditing dependency manifests, and looking up runtime support and end-of-life dates.MIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to inspect project dependency versions, resolve version constraints, and audit Python code for deprecated or incompatible APIs using authoritative evidence and local AST analysis.316 npmMIT
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.16 npmISC
TDQS
Scored across 4 tools
Each tool targets a distinct step of the EOL-checking workflow: enumerating products, fetching release cycles, checking a single version, and scanning project files. There is no overlap; check_version and scan_project differ clearly by input type (single version string vs. file contents).
All four tools follow a clean verb_noun snake_case pattern (list_products, get_cycles, check_version, scan_project). Verbs are chosen precisely to reflect different operations, making the naming predictable and self-documenting.
Four tools is well-scoped for a focused EOL-checking server, with each tool earning its place in the lifecycle. Nothing feels redundant or missing at the count level.
The surface covers discovery, cycle detail, single-version checks, and project scanning, which handles the core workflow end to end. Minor gaps remain, such as no explicit way to enumerate available categories or bulk-check an arbitrary list of versions without a project file.