Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

Related Servers

Alternatives to AWS Health MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      A local MCP server for read-only querying of AWS resources (Lambda, S3) via Boto3, currently exposing a health check tool with planned tools for listing resources and checking free tier.
      7
      -
    • A
      license
      A
      quality
      F
      maintenance
      MCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.
      22
      97 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides typed, audited, least-privilege tools for monitoring AWS infrastructure and GitHub pipelines, including instance health, service status, logs, deployment status, CI workflow runs, failed jobs, and PR checks.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      This MCP server provides tools for inspecting AWS cloud infrastructure, including listing S3 buckets, EC2 instances, and fetching CloudWatch logs using your local AWS credentials.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for running infrastructure health checks with TIBET provenance. It enables users to define, execute, and audit process health checks with dependency chaining and drift tracking.
      6
      MIT

    TDQS

    A3.8/5.0

    Scored across 18 tools

    Disambiguation3/5

    There are systematic org/non-org pairs (get_service_health vs get_org_service_health, get_affected_entities vs get_org_affected_entities, etc.) which are nameable-apart, but the fuzzy boundaries between get_service_health and get_service_events, and between the several overlapping event-listing tools, create real misselection risk.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern (get_, list_, count_, summarize_, find_, check_) with predictable prefixes for org-scoped variants.

    Tool Count4/5

    18 tools is at the upper end but justified by the read-only domain spanning single-account, org-wide, entity, and summary operations. It is slightly heavy but each tool earns a place.

    Completeness4/5

    The surface covers listing, drilling into details, affected entities, counts, summaries, event-type discovery, org-wide views, and an access diagnostic — strong lifecycle coverage for a read-only API. Minor gaps around pagination/continuation handling keep it from a 5.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues