Skip to main content
Glama
oldcoder01
by oldcoder01

Related Servers

Alternatives to AWS MCP Audit

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to run read-only AWS security audits and receive normalized, severity-ranked findings about account posture, such as stale access keys, missing MFA, public buckets, open security groups, and CloudTrail coverage.
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to assess AWS environments against the AWS Security Reference Architecture (SRA) by providing tools to discover, describe, and run security checks across AWS services and accounts.
      5
      3
      Apache 2.0
    • 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
      A
      quality
      C
      maintenance
      Read-only AWS account audit: finds public S3 buckets, missing root and user MFA, unused access keys, world-open security groups, CloudTrail gaps, and forgotten EC2/EBS/RDS spend across every region. Only makes Describe/List/Get calls and runs locally with your own AWS credentials.
      7
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude AI to automatically audit AWS cloud resource configurations, diagnose security vulnerabilities, and generate high-availability optimization reports.
      -

    TDQS

    D1.8/5.0

    Scored across 10 tools

    Disambiguation3/5

    The tools have distinct names suggesting different AWS audit functions, but without descriptions, there is potential ambiguity in overlapping areas like cost analysis (cost_explorer_by_region, cost_explorer_by_service, cost_explorer_summary_tool, cost_signals) and snapshot handling (collect_snapshot, get_snapshot_summary). An agent might struggle to choose between similar-sounding tools without clear purpose differentiation.

    Naming Consistency4/5

    Most tools follow a consistent snake_case pattern with descriptive verb-noun combinations (e.g., collect_snapshot, generate_report, list_findings). However, there are minor deviations like aws_whoami (which uses a command-like name) and cost_explorer_summary_tool (which includes 'tool' redundantly), slightly breaking the pattern.

    Tool Count5/5

    With 10 tools, this server is well-scoped for AWS audit purposes, covering areas like identity (aws_whoami), cost analysis, reporting, snapshot management, and compliance checks. The count is neither too sparse nor overwhelming, allowing for comprehensive audit workflows without unnecessary complexity.

    Completeness3/5

    The tool set appears to cover key audit aspects such as cost analysis, snapshot collection, report generation, and findings listing, but without descriptions, it's unclear if there are gaps in CRUD operations or lifecycle coverage. For example, tools for updating or deleting findings might be missing, potentially limiting agent effectiveness in full audit management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues