ChaosBull MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| simulate_api_failureA | Opens the browser, redirects directly to the user application, and intercepts API requests matching a URL pattern to return an error status code. Checks if a fallback UI element appears. Use to answer: does the app show a proper error state when the payment API returns 503? |
| inject_latencyA | Opens the browser, navigates directly to the user application, and adds artificial delay to requests matching a URL pattern. Observes whether loading indicators or skeleton screens appear. Use to answer: does the app show loading states when the API takes 3 seconds? Does it time out gracefully? |
| block_resourcesA | Opens the browser, navigates to the user application, and blocks requests to specified URL patterns. Simulates third-party outages (analytics, CDNs, tracking) and verifies core content integrity. Use to answer: does the app still load and function if Google Analytics or a CDN is down? |
| simulate_network_dropA | Opens the browser, navigates to the application, and aborts requests matching a pattern after a delay, simulating a mid-flight connection drop. Use to answer: what happens if the network drops after the order request is sent but before the response arrives? |
| trigger_system_network_errorA | Opens the browser, navigates to the application, and aborts requests matching a URL pattern with a system-level network error code, simulating OS-level failures like unreachable hosts or access denied. Use to answer: does the app recover when the DNS resolution fails or the OS rejects a connection? |
| simulate_stateful_failureA | Opens the browser, navigates to the application, and intercepts requests matching a URL pattern. Fails the first N requests with an error status, then lets subsequent requests succeed. Simulates transient failures and tests retry/recovery logic. Use to answer: does the app retry after a 503 and recover when the service comes back? |
| inject_response_corruptionA | Opens the browser, navigates to the application, and intercepts requests matching a URL pattern to return a malformed or corrupted response. Simulates protocol/transport level corruption and observes whether the UI crashes. Use to answer: does the app handle malformed JSON, content-length lies, or truncated payloads without crashing? |
| assert_chaos_handledA | Opens the browser, navigates to the application, and injects a chaos HTTP status into all matching requests. Checks: did the app show fallback UI, were there unhandled exceptions, and did it survive? Use to answer: is the app chaos-resilient — does it show a recovery UI without throwing exceptions? |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |