Skip to main content
Glama
endoflife-mcp

endoflife-mcp

Official

Related Servers

Alternatives to endoflife-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      5
      8
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Verified, dated facts for AI coding agents: what breaks between npm package versions (diffed from TypeScript types), per-version vulnerabilities, the newest version compatible with a given Node/Python/Rust/PHP, end-of-life dates of ~480 runtimes and frameworks, and AI model prices. Covers npm, PyPI, crates.io and Packagist.
      12
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying software product release and support timelines, including EOL dates, active-support end, latest patch, and LTS status for products or specific versions.
      502 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to inspect project dependency and runtime files, determine each component's support status and end dates, and rank upgrade urgency using bundled endoflife.date data.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      3
      1
      MIT

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing products, getting full lifecycle, checking EOL for a specific version, getting risk scores, and scanning a stack. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., list_products, check_eol, scan_stack), making them predictable and easy to understand.

    Tool Count5/5

    Five tools cover the core EOL domain without being too few or too many. Each tool earns its place, providing essential operations for managing end-of-life information.

    Completeness5/5

    The tool set covers the full workflow: discovering products, retrieving lifecycle details, checking EOL status, quantifying risk, and auditing a stack. No obvious missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues