mcp-security-guard
Related Servers
Alternatives to mcp-security-guard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceScans MCP servers for prompt injection, supply chain attacks, excessive permissions, and code execution risks. Includes an offline blacklist that catches known-compromised packages like LiteLLM 1.82.7/1.82.8 and Trivy with zero latency.19MIT
- AlicenseCqualityDmaintenanceSecurity scanner and MCP server that catches dangerous patterns in MCP servers and AI agent projects, such as leaked secrets, shell execution, and prompt-injection text. Runs as both a CLI and MCP server with CI-friendly severity gates.21MIT
- AlicenseAqualityCmaintenanceSecurity scanning for MCP servers from the inside out. Provides runtime inspection, AST-based static analysis, config audit, dependency analysis, and OWASP MCP Top 10 compliance in a single MCP server.5560 npm6MIT
- AlicenseNot gradedqualityBmaintenanceSecurity scanner and runtime proxy for MCP servers. Catches tool poisoning, prompt injection, and rug-pull attacks (silent tool description changes) before they reach your AI agent. Includes a static scanner and a runtime stdio proxy.20 npmMIT
- AlicenseAqualityAmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.1555 npm15Apache 2.0
- AlicenseAqualityDmaintenanceMCP security trust layer. Continuously monitors 800+ MCP packages on npm for install scripts, command injection, hardcoded secrets, capability drift, and publisher posture. Ships a GitHub Action policy gate for PR-level allow/warn/block decisions. 5 MCP tools, no API key required.8221 npm1MIT
TDQS
Scored across 17 tools
The audit and pin families overlap conceptually, but each tool names a distinct target: agent context files, MCP config, server tool definitions, or supply-chain packages. The only mild ambiguity is between audit_server_tools, analyze_tool_definitions, adversarial_test, and security_dashboard scan='full', though their scopes and side effects are explicitly differentiated.
Most tools use predictable snake_case verb_noun names such as audit_mcp_config, pin_tools, and generate_policy. A few outliers like team_status, adversarial_test, and security_dashboard are noun-oriented, but they remain readable and do not break the overall convention.
At 17 tools, the set is slightly heavy but reasonable for a security lifecycle covering audit, pinning, reporting, remediation, policy, and dashboard workflows. No tool appears redundant enough to remove, though the surface is near the upper comfortable range for agent selection.
The toolset covers context and configuration auditing, tool poisoning checks, supply-chain review, adversarial testing, pinning, policy generation, remediation, export, logging, and team reporting. Minor gaps exist around unpinning management and broader runtime enforcement, but core security workflows are well covered.