AWS Fault Injection Simulator MCP Server for chaos engineering. Can mock AZ, DB, and MSK Failure
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":"fis-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.
# FIS MCP Server AWS Fault Injection Simulator (FIS) MCP Server for managing chaos engineering experiments. ## Features - Create and manage FIS experiment templates - Start and stop chaos engineering experiments - List and monitor experiment status - Retrieve AWS resources for targeting ## Installation 1. Install dependencies: ```bash pip install -r requirements.txt ``` 2. Configure AWS credentials: ```bash aws configure ``` ## Usage ### Running the server directly ```bash python index.py ``` ### Using with MCP CLI Add to your MCP configuration: ```json { "mcpServers": { "fis-mcp-server": { "command": "python", "args": ["index.py"], "env": { "AWS_REGION": "us-east-1" } } } } ``` ## Available Tools - `create_experiment_template`: Create a new FIS experiment template - `start_experiment`: Start a chaos engineering experiment - `stop_experiment`: Stop a running experiment - `list_experiment_templates`: List all experiment templates - `get_experiment_template`: Get details of a specific template - `list_experiments`: List all experiments - `get_experiment`: Get details of a specific experiment - `get_aws_resources`: Retrieve available AWS resources for targeting ## Requirements - Python 3.10+ - AWS credentials configured - Appropriate IAM permissions for FIS operations
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.