Chaos-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_code_resilienceA | Runs on-demand, sandbox-isolated mutation testing against a single source file to identify gaps in unit test coverage. Chaos-MCP generates mutants (logical faults like changing |
| triage_test_coverageA | Batch triage: audit a set of files and/or directories and return a weakest-first ranked leaderboard of mutation scores, so you can see where the test suite is most fragile in one call. Directories are recursively expanded to supported source files (.ts/.js/.py/.rs/.php), skipping test files. Files are audited serially. Drill into a weak file with audit_code_resilience for per-mutant survivor detail. |
| estimate_auditA | Cheap pre-flight estimate of how big/long auditing a file will be, WITHOUT running the full mutation test cycle. Returns an approximate mutant count (exact for Rust via cargo-mutants --list; a source heuristic for TS/JS/Python/PHP, labeled fidelity:"approx"). Set withTiming:true to also run the test suite once and estimate wall-clock time. Use this before audit_code_resilience to decide whether to audit now, scope down, or skip. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| harden_file | Walk through hardening one file: audit → write tests for survivors → verify by runId → repeat. |
| triage_changes | Triage a PR's changed files weakest-first, then harden the weakest. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Supported languages | Languages, their mutation engine, line-scope support, and estimate fidelity. |
| Config schema | chaos-mcp.config.json keys with types and meaning. |
| Capabilities overview | The three tools, their arguments, and the triage→audit→verify workflow. |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AraneaDev/Chaos-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server