cloud-audit
Related Servers
Alternatives to cloud-audit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for automated AWS security scanning — 19 modules, risk scoring, zero write operations.3516 npmMIT
- AlicenseAqualityAmaintenanceagent-bom v0.104.0 is an open security scanner and self-hosted control plane for AI, MCP, and cloud infrastructure. The default scan profile in MCP server mode exposes 8 MCP tools. Additional profiles provide inventory, findings, compliance, graph, and runtime workflows.831Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server for automated AWS security scanning. It detects over-privileged IAM roles and S3 Public Access Block misconfigurations, enabling least-privilege enforcement through tools like list_iam_roles, analyze_iam_policy, and analyze_s3_security.MIT
- FlicenseNot gradedqualityCmaintenanceA read-only MCP server for inspecting AWS resources, detecting misconfigurations, and estimating costs across EC2, S3, and IAM, enabling agents to safely query and analyze cloud infrastructure.-
- AlicenseAqualityCmaintenanceA local-first AWS security tool that uses graph theory to discover attack paths (e.g., Internet → Role → DB) and prioritize remediations. It allows agents to perform read-only security audits and generate Terraform fixes without data exfiltration.1520 PyPI4Apache 2.0
- AlicenseAqualityAmaintenanceSecurity MCP server with 300+ rules for AI-generated code. Scans Next.js, Supabase, Clerk, Stripe, Prisma, Hono, GraphQL and 20+ modules. Zero config, runs locally.39312 npm5Apache 2.0
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: scan initiates, findings/attack_chains/health_score retrieve different result aspects, remediation is action-oriented, list_checks is informational. No overlapping or ambiguous boundaries.
All tool names follow a consistent verb_noun pattern (scan_aws, get_findings, get_attack_chains, get_remediation, get_health_score, list_checks). The pattern is predictable and uniform across the set.
With 6 tools, the server is well-scoped for a security audit domain. Each tool serves a distinct purpose in the scan-retrieve-remediate workflow, and the count is within the ideal range for coherent tool sets.
The tool surface covers the core workflow: initiating scans, retrieving findings, attack chains, health score, remediation, and listing checks. A minor gap is the lack of a tool to export or compare scans, but the primary lifecycle is complete and agents can operate without dead ends.