GuardianMCP
Related Servers
Alternatives to GuardianMCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceScans Python, Node.js, Java/Spring, and PHP dependency manifests for known vulnerabilities using OSV and GitHub Advisory APIs.-

@guardbee/mcp-dependencyofficial
AlicenseNot gradedqualityFmaintenanceEnables 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.796 npmMIT- AlicenseAqualityDmaintenanceAI-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.3Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to submit npm, PyPI, Go, or Maven packages and manifests to the free OSV.dev database and receive per-package and per-advisory results with CVE mappings, CVSS scores, severities, and the versions that fix each issue. It also supports filtering by minimum severity, de-duplicating alias advisories, and machine-readable error/warning rows for CI gates and upgrade recommendations.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityCmaintenanceEnables 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.36 npmMIT
TDQS
Scored across 1 tool
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.
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.
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.
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.