Skip to main content
Glama
Kranny36

eosl-mcp

by Kranny36
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to eosl-mcp

No user-submitted related servers found.

    Related Servers

    • endoflife-mcp by endoflife-ai

      endoflife-mcpofficial

      endoflife-ai
      A
      license
      A
      quality
      A
      maintenance
      Software 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.
      5
      11 npm
      MIT

    • 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
      11 npm
      MIT

    • mcp-endoflife

      pipeworx-io
      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.
      42 npm
      MIT

    • frontdesk-review

      AlexandDunk
      F
      license
      Not graded
      quality
      A
      maintenance
      Sourced product prices, dated price history, specs and independent-test coverage across 4,764 hardware products and 2,064 software vendors — every figure returned with its source URL and the date it was captured. Unknown values come back as null rather than a guess, so an agent can cite what it surfaces.
      -
    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.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: bulk_check for multi-part lookups, lookup_part for single-part lookup, search_models for discovery by name, list_vendors for vendor enumeration, and get_family for detailed family records. Descriptions explicitly cross-reference each other, eliminating ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: bulk_check, search_models, list_vendors, lookup_part, get_family. The verbs are clear and the pattern is uniform.

    Tool Count5/5

    Five tools is well-scoped for a read-only EOSL database: two lookup tools (single/bulk), two discovery tools (vendors/models), and one detail tool. Each serves a necessary function without redundancy.

    Completeness5/5

    The surface covers the full read-only query lifecycle: vendor discovery (list_vendors), model discovery (search_models), single-part lookup (lookup_part), bulk lookup (bulk_check), and deep family detail (get_family). No obvious gaps for the domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources