Skip to main content
Glama
Kalvisan

GuardianMCP

by Kalvisan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to GuardianMCP

No user-submitted related servers found.

    Related Servers

    • @guardbee/mcp-dependency-auditor by GuardBee

      @guardbee/mcp-dependencyofficial

      GuardBee
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables auditing npm, pip, and other package dependencies for known CVEs via the OSV database, with tools to scan manifests, query individual packages, and integrate into CI/CD workflows.
      99 npm
      MIT

    • DepsGuard MCP

      Kim-Kyowon
      A
      license
      A
      quality
      D
      maintenance
      AI-powered dependency vulnerability and breaking change analyzer that scans dependencies, identifies vulnerabilities via OSV.dev, and uses AI to assess real impact and suggest fixes.
      3
      Apache 2.0

    • Depfender MCP Server

      depfenderdev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to scan software packages for data exfiltration and security threats directly within their IDE across npm, PyPI, Cargo, and Maven ecosystems. This tool helps ensure the safety of project dependencies by identifying potential risks before they are integrated.
      MIT

    • Dependency Checker MCP Server

      djodjonx
      A
      license
      B
      quality
      C
      maintenance
      Enables security scanning for npm dependencies by checking manifest and lockfiles against the OSV.dev and Socket.dev vulnerability databases. It provides tools to detect vulnerabilities in specific packages and retrieve detailed technical reports for identified security issues.
      3
      2 npm
      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

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'check_vulnerabilities' has a clear, distinct purpose focused on security vulnerability scanning.

    Naming Consistency5/5

    The tool name 'check_vulnerabilities' follows a consistent verb_noun pattern, and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and appropriate for its function.

    Tool Count2/5

    A single tool for a security vulnerability scanning server is too limited in scope. While the tool is well-described, a server with only one tool often feels thin and lacks the breadth needed for comprehensive security operations, such as managing scans, updating databases, or handling different file types beyond the mentioned ones.

    Completeness2/5

    The tool surface is severely incomplete for a security vulnerability domain. It only covers scanning for vulnerabilities in specific dependency files, missing essential operations like configuring scan settings, retrieving historical scan results, updating vulnerability databases, or integrating with other security tools. This creates significant gaps that could lead to agent failures in broader security workflows.

    Resources