Resilience Architect MCP
Related Servers
Alternatives to Resilience Architect MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAnalyzes DevOps findings to automatically recommend and generate AWS Fault Injection Simulator (FIS) experiment templates. It helps teams validate system resilience by mapping reported issues to specific chaos engineering actions across AWS services.MIT
- AlicenseNot gradedqualityCmaintenanceEnables state-aware Terraform/OpenTofu plan evaluation against live AWS topology and CloudWatch telemetry, detecting reliability blast radius and FinOps waste before merge.Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents and SREs to diagnose Kubernetes incidents, perform root cause analysis, and generate safety-guardrailed GitOps remediation patches or kubectl commands. It supports live clusters, Alertmanager webhooks, and offline simulation scenarios.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform chaos engineering and resilience testing on Kubernetes clusters through Chaos Mesh. Supports creating and managing 24 types of chaos experiments including network failures, stress tests, pod disruptions, and I/O faults through natural language conversations.2MIT
- AlicenseBqualityBmaintenanceEnables developers to audit MCP tool schemas and annotations, multi-agent delegation graphs, multi-turn behavioral drift, bias, and token/cost telemetry from inside their IDE or CLI, and to generate EU AI Act, NIST AI RMF, and SOC 2 compliance dossiers. It also provides sub-250ms inline circuit-breaking, adversarial IPIP-NEO-120 persona cohorts, stress testing, and chaos fault injection.121,313 npm1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables users to investigate infrastructure incidents in plain English, correlate observability and deploy data with runbooks, and get evidence-backed root-cause proposals with approval-gated remediation.5-
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: FIS experiment vs template operations, Resource Explorer view management, resource search vs relationship discovery. The names and descriptions make boundaries clear, and there is no significant overlap that would cause misselection.
All tools follow a consistent CamelCase verb-noun pattern (e.g., GetFISExperiment, ListFISExperiments, CreateFISExperimentTemplate). Service prefixes are used consistently within FIS tools, and minor variations like GetStackResources vs ListCloudFormationStacks are justified by different actions.
13 tools is well-scoped for a resilience architecture server covering FIS, Resource Explorer, CloudFormation, and Config. Each tool serves a distinct operation without redundancy, fitting comfortably in the ideal 3-15 range.
The surface covers discovery, template creation/update, and experiment start, but lacks critical lifecycle operations like stopping an experiment, deleting templates, and deleting/updating Resource Explorer views. These gaps could hinder full workflow execution for an agent.