Skip to main content
Glama
MalkiLevinzon

Vulnerability Registry MCP Server

by MalkiLevinzon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Vulnerability Registry MCP Server

No user-submitted related servers found.

    Related Servers

    • vulnerability-registry-mcp

      feldboy
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables security analysts and risk managers to query a legacy CVE registry via natural language, providing tools for searching vulnerabilities, retrieving details, and obtaining statistics.
      -

    • NVD/NIST MCP server

      d4ngkh04w
      A
      license
      A
      quality
      B
      maintenance
      Enables users to search and retrieve CVE records, CVE history, CPE Dictionary entries, and CPE match criteria through MCP tools, with local caching, pagination, and upstream rate-limit handling.
      10
      MIT

    • nvd-cve-mcp-server

      millsks
      A
      license
      A
      quality
      C
      maintenance
      MCP server that provides tools to search, filter, and retrieve CVE data from the NVD API, including by ID, keyword, severity, and recency.
      4
      MIT

    • NVD-MCP

      aim-sec
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for searching NIST's National Vulnerability Database, enabling retrieval of recent CVEs, keyword/CPE/CWE searches, and detailed CVE information.
      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 targets a distinct operation: get_vulnerability for a specific CVE, search_vulnerabilities for filtered lists, search_vendors for vendor lookup, get_vendor_overview for aggregate vendor data, and get_vulnerability_statistics for counts. There is no meaningful overlap between any pair of tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase and underscores, with verbs limited to 'get' and 'search'. The naming clearly indicates whether a tool returns a single entity, a list, or statistics.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a vulnerability registry query interface. Each tool covers a distinct need without redundancy or bloat, fitting comfortably in the ideal 3-15 range.

    Completeness5/5

    The tool set provides complete read-only coverage for a vulnerability registry: individual CVE lookup, flexible searching, vendor discovery, vendor-specific aggregation, and vulnerability statistics. No obvious gaps exist for the apparent domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources