Skip to main content
Glama

Related Servers

Alternatives to vuln-priority

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables CVE lookups and risk assessment by integrating CISA Known Exploited Vulnerabilities (KEV) data and CVSS metrics. It helps users prioritize patching efforts by ranking vulnerabilities based on exploitation status and calculated risk scores.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to look up CVE details, EPSS exploit probability, and CISA KEV status from free public APIs to prioritize vulnerabilities by real-world risk. Combines these sources into a single enriched, prioritized view using a KEV > EPSS > CVSS rule.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides real-time vulnerability intelligence including CVE lookup, EPSS exploit probability, and CISA KEV status from free APIs, enabling AI assistants to prioritize CVEs by real-world risk.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables searching and analyzing CVEs and vulnerabilities from multiple sources, optimized for PR review scenarios to help developers identify the latest security issues.
      8
      2
      -

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: package_vulns checks package versions, prioritize_vulns ranks CVE IDs, recent_exploited shows newly added KEV entries, and vuln_details provides deep dive on a single CVE. No two tools overlap in their primary function.

    Naming Consistency3/5

    Tool names mix conventions: 'prioritize_vulns' follows verb_noun, but 'package_vulns' and 'vuln_details' are noun phrases, and 'recent_exploited' is adjective+past participle. The naming is readable and consistent in style (lowercase underscores) but lacks a uniform verb_noun pattern.

    Tool Count5/5

    With 4 tools, the server is tightly scoped to its purpose of vulnerability prioritization. Each tool covers a distinct workflow step, and none feel redundant or unnecessary.

    Completeness4/5

    The surface covers the core workflows: checking packages, ranking CVEs, viewing recent exploited vulnerabilities, and retrieving detailed information. Minor gaps exist (e.g., no direct way to list all vulnerabilities for a package beyond the top 50), but agents can still accomplish the intended tasks without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues