Skip to main content
Glama

Related Servers

Alternatives to cloud-audit

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      agent-bom 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. See the published Glama release for its packaged version.
      8
      727 PyPI
      35
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes read-only AWS security-posture checks as MCP tools, letting Claude Desktop, Claude Code and Cursor run 14 severity-ranked checks across S3, EC2, RDS, IAM and CloudTrail, describe resources, and produce a scored summary with prioritized risks. It ships an offline fixture estate so every tool works without credentials, and switches to a live account via a single environment variable.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A 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.
      15
      28 PyPI
      4
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: scanning, listing checks, retrieving findings, health scores, attack chains, remediation, and agent blast radius. No two tools overlap in purpose; even get_health_score and get_findings differ (summary vs. detailed list).

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: scan_aws, list_checks, get_findings, get_health_score, get_attack_chains, get_remediation, get_agent_blast. The verbs (scan, list, get) are used predictably, and the nouns clearly indicate the resource.

    Tool Count5/5

    Seven tools is ideal for the domain of AWS security scanning: they cover the entire workflow from initiating a scan to viewing results, details, and remediation. Each tool is necessary and there is no bloat.

    Completeness4/5

    The tool set covers the full lifecycle: scan, list checks, get findings, get health score, get attack chains, get remediation, and even a specialized agent blast tool. The only minor gap is that there is no direct tool to initiate a specific check or re-scan a particular resource, but the existing tools allow agents to achieve the core goals.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues