Skip to main content
Glama
endoflife-ai

endoflife-mcp

Official
by endoflife-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to endoflife-mcp

No user-submitted related servers found.

    Related Servers

    • EOL MCP Server

      ducthinh993
      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

    • EndOfLife MCP Server

      brianprost
      A
      license
      A
      quality
      F
      maintenance
      Provides access to the endoflife.date API to query support and end-of-life information for thousands of software products. It enables users to retrieve detailed release schedules, lifecycle data, and product categories through natural language.
      16
      7
      15 npm
      MIT

    • oss-intel-mcp

      FoundryNet
      A
      license
      Not graded
      quality
      F
      maintenance
      Open source intelligence for AI agents — GitHub project-health scoring, package dependency-risk analysis, trending repositories, license checks, and side-by-side package comparison.
      MIT

    • eosl-mcp

      Kranny36
      A
      license
      A
      quality
      A
      maintenance
      Source-backed hardware end-of-life (EOL/EOSL) lookups by part number for enterprise gear — support status, end-of-sale and end-of-support dates, with the vendor's own bulletin URL on every answer. Unknown parts return found:false, never a guess.
      5
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityActive
    ResponsivenessNo issues

    Resources