Skip to main content
Glama

Related Servers

Alternatives to @gnaws/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous DevOps agents to detect out-of-band AWS resources, calculate monthly FinOps burn, and generate Terraform/OpenTofu import blocks or safe purge scripts through hardened MCP tools.
      73 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to analyze AWS cloud costs, audit for wasted resources like stopped EC2 instances and unattached EBS volumes, and check budget status through natural language in any MCP-compatible AI assistant. Supports multi-profile and multi-region querying while keeping AWS credentials local to the user's machine.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query multi-cloud costs, inventory, waste, and commitments across AWS, GCP, Cloudflare, and OVH through read-only MCP tools.
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to query and analyze AWS cloud costs, audit for waste, and monitor budgets through natural language in MCP-compatible AI assistants, while keeping AWS credentials local.
      -
    • F
      license
      Not graded
      quality
      D
      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.
      -

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct action (scan live, load offline, detect orphans, export graph, dump raw data, list regions, show status), but export and dump both involve saving data and detect can also write findings to a file, creating mild overlap. Overall boundaries are clear enough for an agent to select correctly.

    Naming Consistency5/5

    All tool names are single lowercase words following a simple command-style convention (scan, load, detect, export, dump, status). The only non-verb, regions, still fits the same flat lowercase pattern, so there is no style mixing.

    Tool Count5/5

    Seven tools is well-scoped for an AWS resource graph scanning and orphan detection server. Each tool supports a distinct stage in the workflow without redundancy or bloat.

    Completeness4/5

    The core workflow is complete: scan or load builds the graph, status confirms readiness, regions summarizes scope, detect finds orphans, dump enables offline reuse, and export produces output. A minor gap is the lack of a direct resource-listing/query tool, though export formats can serve that purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues