MCP Security Scanner
Related Servers
Alternatives to MCP Security Scanner
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables security scanning of code projects to identify common vulnerabilities like XSS, injections, SSRF, and path traversal issues. Provides local, offline scanning with severity-grouped results and actionable fix suggestions for improving code security.38 npm-
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive security scanning of code repositories to detect secrets, vulnerabilities, dependency issues, and configuration problems. Provides real-time security checks and best practice recommendations to help developers identify and prevent security issues.7 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables security scanning of codebases through integrated tools for secret detection, SCA, SAST, and DAST vulnerabilities, with AI-powered remediation suggestions based on findings.MIT
- AlicenseNot gradedqualityAmaintenanceDetect live website vulnerabilities and security flaws in GitHub repositories using automated DAST and SAST scanning. Safeguard applications by identifying exposed secrets, insecure dependencies, and common code patterns prone to exploitation. Receive structured fix plans with precise code remediation steps to resolve identified risks and improve security posture.2MIT
- AlicenseNot gradedqualityDmaintenanceAutomatically detects security vulnerabilities in AI-generated code, scanning for hardcoded secrets, injection flaws, XSS, weak cryptography, authentication issues, path traversal, and vulnerable dependencies across JavaScript, Python, Java, and Go.12 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables scanning projects for dependency vulnerabilities, secrets, license conflicts, code quality, and git health, returning a 0-100 health score with actionable suggestions.7 npmMIT
TDQS
Scored across 4 tools
The tools have overlapping purposes that could cause confusion. 'scan_code_vulnerabilities' and 'scan_secrets' both scan source code, and 'generate_security_report' appears to aggregate results from the other scans, creating ambiguity about when to use it versus the individual scan tools. However, the descriptions help clarify their specific focuses, preventing complete misselection.
All tool names follow a consistent snake_case pattern with a clear 'verb_noun' structure: 'generate_security_report', 'scan_code_vulnerabilities', 'scan_dependencies', and 'scan_secrets'. This predictability makes it easy for an agent to understand and navigate the toolset.
With 4 tools, the count is well-scoped for a security scanner server. Each tool serves a distinct function within the domain, and there are no extraneous or missing tools that would make the set feel too thin or bloated.
The toolset covers key security scanning areas: code vulnerabilities, dependencies, and secrets, with a reporting tool to aggregate results. Minor gaps exist, such as the lack of tools for remediation actions or scanning configuration files, but agents can work around these by using the provided tools effectively for core workflows.