Skip to main content
Glama
Sidd27

infrawise

by Sidd27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to infrawise

No user-submitted related servers found.

    Related Servers

    • LensPR

      kyrylopr
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that builds a dependency graph of your codebase, giving AI agents structural understanding to analyze impact, find context, and make safe modifications across languages and infrastructure.
      MIT

    • aws-mcp

      RafalWilinski
      F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with your AWS environment. This allows for natural language querying and management of your AWS resources during conversations. Think of better Amazon Q alternative.
      3
      295
      -

    • Cost Management MCP

      knishioka
      A
      license
      B
      quality
      C
      maintenance
      An MCP server for unified cost tracking and analysis across AWS, OpenAI, and Anthropic. It enables users to query expenditures, compare costs across providers, and analyze usage trends through natural language.
      10
      MIT

    • aws-readonly-mcp

      ziyuyu23
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that lets an LLM inspect an AWS account — list EC2 instances, S3 buckets, IAM users, and cost — with a structural guarantee against any mutations.
      MIT

    • SilentFail

      decksaga
      A
      license
      Not graded
      quality
      C
      maintenance
      Diagnose MCP servers — health checks, tool testing, token cost audits, conflict detection, and security scanning with 50+ prompt injection patterns. Works as CLI or MCP server inside Claude Desktop.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct AWS resource or analysis action (queues, topics, secrets, lambdas, caches, etc.), and the two overview tools (get_infra_overview vs get_graph_summary) are explicitly disambiguated by depth. The four index suggestion tools are clearly separated by database engine (DynamoDB, Postgres, MongoDB, MySQL). No two tools appear to duplicate the same purpose.

    Naming Consistency3/5

    The majority of tools follow a consistent get_<resource>_overview/details pattern, but the index suggestion tools mix conventions: suggest_gsi, suggest_mongo_index, postgres_index_suggestions, and mysql_index_suggestions have inconsistent verb positioning and naming order. analyze_function also breaks the get_ prefix pattern, though the overall naming remains readable and predictable enough to navigate.

    Tool Count4/5

    At 22 tools, the set is on the heavy side, but the server's scope covers a broad range of AWS services (messaging, storage, compute, caching, edge, auth, IaC), so each resource-specific getter earns its place. A few tools could be consolidated (e.g., the four index suggestors), but the count is justified by the domain's breadth.

    Completeness4/5

    The tool surface covers the major infrastructure categories an agent would need for AWS: compute, queues, topics, secrets, parameters, databases, streams, API routes, caching, CDN, auth, logs, and IaC outputs. Minor gaps exist—for example, no VPC/networking details and no DynamoDB TTL or stream consumer depth—but core workflows like query tuning, security review, and event-shape lookup are well supported.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources