Production-ready MCP server for monitoring AWS Health events and service status
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"aws-health-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# AWS Health MCP Server > **Disclaimer:** This AWS content is provided subject to the terms of the AWS Customer Agreement available at https://aws.amazon.com/agreement or other written agreement between the Customer and Amazon Web Services. This is sample code for demonstration purposes only. It is not intended for production use. You should work with your security and legal teams to meet your organizational security, regulatory, and compliance requirements before any deployment. MCP server that exposes AWS Health API as tools. Works with Claude Desktop, Kiro or any MCP-compatible client. 📖 **Blog:** [Building an AWS Health MCP Server for Agentic Operations](https://medium.com/@jsanketh1799/building-an-aws-health-mcp-server-for-agentic-operations-cda234012e38) ## Prerequisites - Python 3.10+ - AWS credentials configured (`aws configure` or environment variables) - AWS **Business or Enterprise Support** plan (required for Health API) - For org-level tools: AWS Organizations with Health service access enabled ## Setup Add this to your MCP config file: - **Claude Desktop**: `~/Library/Application Support/Claude/claude_desktop_config.json` - **Kiro**: `~/.kiro/settings/mcp.json` - **Amazon Q CLI**: `~/.aws/amazonq/mcp.json` ### Using uvx from PyPI (recommended) ```json { "mcpServers": { "aws-health": { "command": "uvx", "args": ["aws-health-mcp-server"], "env": { "AWS_PROFILE": "default" } } } } ``` ### Using pip ```bash pip install aws-health-mcp-server ``` ### From a local clone ```json { "mcpServers": { "aws-health": { "command": "uv", "args": ["run", "--directory", "/path/to/aws-health-mcp-server", "aws-health-mcp-server"], "env": { "AWS_PROFILE": "default" } } } } ``` That's it. `uv` handles the venv and dependencies automatically. ## Tools ### Account-Level | Tool | Description | |------|-------------| | `get_service_health` | All active health events | | `g…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.