Skip to main content
Glama
aws-samples

AWS Health MCP Server

Official
by aws-samples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to AWS Health MCP Server

No user-submitted related servers found.

    Related Servers

    • AWS Resource MCP

      herrerogusano
      F
      license
      A
      quality
      B
      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
      -

    • health-monitor-mcp

      oaslananka
      A
      license
      A
      quality
      B
      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
      92 npm
      2
      MIT

    • Frank MCP Server

      cbuckley-code
      F
      license
      Not graded
      quality
      C
      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.
      -

    • mcp-aws

      Preeti325
      A
      license
      Not graded
      quality
      C
      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.
      2 npm
      MIT

    • tibet-pol-mcp

      Humotica
      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
    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

    A3.6/5.0

    Scored across 11 tools

    Disambiguation3/5

    The org-prefixed mirror set is a coherent pattern, but several pairs overlap heavily: get_service_health vs get_service_events (both return current event data for a service), and get_org_account_events vs get_org_health_events (the latter already filters by account_id). Descriptions help somewhat but the 'health' vs 'events' distinction is subtle enough to cause misselection.

    Naming Consistency5/5

    Every tool follows a strict get_<scope>_<resource> snake_case pattern with a consistent 'org' prefix to mark organization-wide variants. Naming is fully predictable and readable.

    Tool Count4/5

    11 tools is within a reasonable range, but roughly half are org-scope duplicates of single-account tools, so the effective unique surface is smaller than the count suggests.

    Completeness4/5

    Covers active/upcoming events, per-service and per-account queries, scheduled changes, affected entities, and completed history across both single-account and org scopes. A dedicated get-event-by-ARN details tool is missing but not a hard blocker.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources