agent-security-scanner-mcp
Related Servers
Alternatives to agent-security-scanner-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceSecurity scanner for AI agent packages that enables AI agents to audit MCP servers and packages for vulnerabilities, prompt injection, and supply chain attacks.5118 npm3AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceProvides a security scanner for AI agent skills and MCP servers, detecting threats like prompt injection, identity hijacking, and memory poisoning.26 npm2MIT
- AlicenseBqualityCmaintenanceProvides local, dependency-free security scanning tools for LLM configurations, prompts, RAG sources, and more, enabling AI coding agents to detect prompt injections and other vulnerabilities without external network access.8MIT
- AlicenseNot gradedqualityCmaintenanceReal security scanners for AI coding agents — SAST (441 rules), secret detection (419+ patterns), dependency CVEs (OSV.dev), MCP/skill vetting, MITRE ATT&CK. Open-source, Rust, free7 npmApache 2.0

AgentAuditofficial
AlicenseAqualityDmaintenanceEnables AI agents to scan MCP servers and AI packages for vulnerabilities, prompt injection, and supply chain attacks.7118 npmAGPL 3.0- AlicenseNot gradedqualityBmaintenanceMCP security scanner for AI agents - detects prompt injection, secrets, PII, and vets MCP servers before installationApache 2.0
TDQS
Scored across 22 tools
Tools are mostly distinct with specific targets (e.g., packages, SBOM, files, projects, skills, prompts, actions). Some overlap exists between check_package, sbom_check_hallucinations, and scan_packages, but descriptions clarify levels. The deprecated alias clawproof_health introduces minor confusion.
Naming conventions are mixed: some use 'check_', 'evaluate_', 'fix_', 'get_', 'list_', 'sbom_', 'scan_', 'score_'. Within groups (sbom_*, scan_*) it is consistent, but overall there is no single verb_noun pattern across all tools.
22 tools is well-scoped for a security scanner MCP server covering many scanning types (files, projects, skills, prompts, actions, SBOM, compliance). Each tool serves a distinct purpose without being excessive.
Covers a broad range of security scanning needs: vulnerability scanning, hallucination detection, SBOM generation and analysis, compliance evaluation, and AIVSS scoring. Minor gaps like container scanning or dependency updates, but core workflows are well-covered.