Skip to main content
Glama
Agam-S

Vulnary-MCP

by Agam-S
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Vulnary-MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • vuln-nist-mcp-server

      HaroldFinchIFT
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for querying the NIST National Vulnerability Database (NVD) API, enabling search and retrieval of CVE details, temporal context, and KEV catalog entries.
      14
      MIT

    • kr.ai.vdb/vdb

      0pstech
      A
      license
      A
      quality
      B
      maintenance
      MCP server for checking packages against an AI-aware vulnerability database, including CVEs, slopsquatting, CISA KEV, and MCP-server trust profiles.
      10
      54 PyPI
      Elastic 2.0

    • GhostFree

      shane-js
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that scans repository dependencies for known vulnerabilities (CVEs) using OSV.dev, enriches findings with NVD and CISA KEV data, and supports triage, remediation, and accepted risk management directly from an AI coding assistant.
      6
      30 npm
      1
      MIT
    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

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct use case: CVE lookup, single-package query, batch dependency scan, and manifest file parsing. The overlap between check_package and scan_dependencies is well-delineated by single-item vs. batch/list operations, so an agent should not misselect.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern with purposeful verbs: lookup, check, scan, scan. This makes the action and target of each tool predictable and easy to reason about.

    Tool Count5/5

    Four tools is a well-scoped set for a vulnerability lookup and dependency scanning server. Each tool earns its place and there is no redundancy or unnecessary bloat.

    Completeness5/5

    The tool surface covers the core vulnerability workflow: fetching CVE details, querying a single package, scanning a dependency list, and parsing a manifest file. No significant lifecycle or workflow gaps exist for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources