Which integrations are available for this server?

Allows AI agents to block or simulate outages of Google Analytics requests during browser tests, verifying that core application functionality remains intact without analytics. Allows AI agents to block or simulate failures of Hotjar tracking requests to test whether the app remains functional when third-party analytics tools are unavailable. Allows AI agents to simulate payment gateway outages by intercepting payment API requests and forcing error responses, such as when Stripe is down, to verify fallback UI and resilience.

How do I use ChaosBull MCP?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ChaosBull MCP Force a 503 on the checkout API and verify the fallback banner appears." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

ChaosBull MCP

by Omkar2240

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

ChaosBull MCP 🐂💥

License: MIT MCP Version Playwright

Dynamic browser network chaos engineering & resilience testing for AI agents and developers.
Your tests run on perfect networks. Your users don't. ChaosBull lets AI agents unleash controlled network havoc on web pages to verify they don't break in production.

📖 New to Chaos Engineering or looking for an intuitive explanation? Check out our First Principles Guide for Non-Tech Minds explaining how ChaosBull works using everyday analogies.

⚡ Why ChaosBull?

Continuous Integration (CI) and local dev environments have flawless connectivity:

APIs respond in 15 milliseconds.
CDNs never glitch.
Cellular handoffs and elevator dead zones do not exist.

Then your code ships to real humans — and production breaks when a payment gateway returns a 503, analytics scripts hang and block page hydration, or a mobile user enters an underground tunnel mid-checkout.

AI agents writing tests or performing QA normally have no dynamic control over the network layer inside real browser sessions. They can't ask:

🙈 Does the checkout page display a polite fallback banner if Stripe is down?
🙈 Does the dashboard show skeleton loaders when the API takes 3 seconds?
🙈 Does the application function normally if third-party tracking scripts are blocked?
🙈 What happens if the network drops right after the user taps "Place Order"?
🙈 Does the app automatically retry and recover from transient 503 errors?

ChaosBull gives AI agents and automated workflows the power to charge into your network layer, sabotage connections on demand, and assert whether your app survives.

Related MCP server: web-ui-tester

🛠️ The 8 ChaosBull Superpowers

                    ┌──────────────────────────────────────────────┐
                    │               ChaosBull Engine               │
                    └──────────────────────┬───────────────────────┘
                                           │
         ┌──────────────────┬──────────────┴─────┬──────────────────┐
         │                  │                    │                  │
         ▼                  ▼                    ▼                  ▼
  API Failures         Latency & Jitter      Mid-Flight Drops    Resource Blocks
 (500/502/503/etc)     (Slow 3G/Timeouts)     (Aborted Streams)  (Ads/Analytics)
         │                  │                    │                  │
         ▼                  ▼                    ▼                  ▼
  OS Network Drops     Transient Retries     Corrupted Payloads  Resilience Verdict
(DNS/EAI_AGAIN/Abort)  (Fail N -> Succeed)   (Truncated/Bad JSON) (Pass/Fail Score)

1. `simulate_api_failure`

Intercepts requests matching a URL pattern and forces them to return an error HTTP status code. Verifies if the frontend renders a fallback UI element instead of crashing.

{
  "url": "https://example.com/checkout",
  "intercept_pattern": "**/api/payment**",
  "status_code": 503,
  "response_body": "{\"error\":\"Service Unavailable\"}",
  "fallback_selector": ".error-boundary",
  "wait_ms": 2000
}

Output:

{
  "url": "https://example.com/checkout",
  "intercept_pattern": "**/api/payment**",
  "intercepted_count": 1,
  "intercepted_requests": [
    { "url": "https://example.com/api/payment", "method": "POST", "status": 503 }
  ],
  "fallback_found": true,
  "fallback_selector": ".error-boundary",
  "page_state": {
    "page_errors": [],
    "console_errors": ["Failed to load resource: the server responded with a status of 503"]
  },
  "wait_time_ms": 2000
}

2. `inject_latency`

Injects deliberate delays and jitter into matching requests to simulate slow mobile connections, saturated links, or overloaded backend services. Checks if loading skeletons appear.

{
  "url": "https://example.com/dashboard",
  "intercept_pattern": "**/api/stats**",
  "latency_ms": 3000,
  "jitter_ms": 500,
  "loading_selector": ".skeleton-card"
}

Output:

{
  "url": "https://example.com/dashboard",
  "intercept_pattern": "**/api/stats**",
  "intercepted_count": 1,
  "intercepted_requests": [
    { "url": "https://example.com/api/stats", "method": "GET", "delay_ms": 3218 }
  ],
  "loading_state_found": true,
  "page_state": { "page_errors": [], "console_errors": [] },
  "load_time_ms": 3410
}

3. `block_resources`

Aborts matching requests outright to simulate third-party outages (e.g., Google Analytics, Tag Manager, Hotjar, external CDN font providers). Asserts whether the core app UI remains functional.

{
  "url": "https://example.com",
  "block_patterns": ["**/analytics**", "*.doubleclick.net/**", "**/tracker.js"],
  "core_content_selector": "#main-app-content",
  "wait_ms": 2000
}

Output:

{
  "url": "https://example.com",
  "block_patterns": ["**/analytics**", "*.doubleclick.net/**", "**/tracker.js"],
  "blocked_count": 3,
  "blocked_urls": ["https://example.com/analytics.js", "https://stats.doubleclick.net/collect"],
  "core_content_found": true,
  "page_state": { "page_errors": [], "console_errors": [] },
  "wait_time_ms": 2000
}

4. `simulate_network_drop`

Simulates sudden connection loss mid-stream (like entering a subway tunnel) by aborting in-flight requests after a defined delay.

{
  "url": "https://example.com/cart",
  "intercept_pattern": "**/api/order/submit**",
  "drop_after_ms": 400,
  "fallback_selector": ".offline-alert",
  "wait_ms": 2000
}

5. `trigger_system_network_error`

Fails requests with low-level OS/protocol socket errors: addressunreachable (DNS failure), connectionaborted (reset by peer), accessdenied (firewall blocks), or aborted.

{
  "url": "https://example.com/feed",
  "intercept_pattern": "**/api/**",
  "error_code": "addressunreachable",
  "fallback_selector": ".dns-fail-banner",
  "wait_ms": 1500
}

6. `simulate_stateful_failure`

Fails the first $N$ requests with an error status (e.g., 503), then allows subsequent requests to succeed. Verifies if client-side retry/backoff mechanisms recover automatically without user intervention.

{
  "url": "https://example.com/reports",
  "intercept_pattern": "**/api/generate**",
  "http_status": 503,
  "failure_count": 2,
  "success_payload": "{\"status\":\"ready\",\"reportId\":\"12345\"}",
  "fallback_selector": ".retry-indicator",
  "wait_ms": 3000
}

7. `inject_response_corruption`

Feeds damaged payloads to the browser:

malformed_json: Incomplete or broken JSON objects.
length_mismatch: Content-Length header advertises 99,999 bytes, but only sends 20 bytes.
truncated: Payload severed at truncate_at_byte.

Tests if client JSON parsers crash the JavaScript runtime or fail cleanly.

{
  "url": "https://example.com/profile",
  "intercept_pattern": "**/api/user**",
  "corruption_type": "malformed_json",
  "fallback_selector": ".data-error-notice",
  "wait_ms": 2000
}

8. `assert_chaos_handled`

The ultimate resilience test. Injects failure into target endpoints and executes an automated inspection:

Did unhandled JavaScript exceptions occur? (page_errors)
Did console errors cascade out of control?
Did the designated fallback/error recovery UI appear?
Calculates chaos_survived: true | false.

{
  "url": "https://example.com/pricing",
  "intercept_pattern": "**/api/tiers**",
  "http_status": 500,
  "expected_fallback_selector": ".error-fallback-container",
  "wait_ms": 2000
}

Output:

{
  "url": "https://example.com/pricing",
  "intercept_pattern": "**/api/tiers**",
  "http_status": 500,
  "unhandled_exceptions": [],
  "console_errors": ["Failed to load resource: status 500"],
  "fallback_ui_detected": true,
  "expected_fallback_selector": ".error-fallback-container",
  "chaos_survived": true,
  "wait_time_ms": 2000
}

🔌 1-Minute Setup

You do not need to manually clone or install anything. Just add ChaosBull to your AI assistant:

Cursor, Claude Desktop, Antigravity & Windsurf

Add this to your MCP configuration (claude_desktop_config.json, .cursor/mcp.json, or IDE MCP settings):

{
  "mcpServers": {
    "chaosbull": {
      "command": "npx",
      "args": ["-y", "chaosbull"]
    }
  }
}

Cursor UI Shortcut: Go to Settings ➔ MCP ➔ Add New MCP Server:
Name: chaosbull
Type: command
Command: npx -y chaosbull

That's it! Your AI assistant will automatically launch ChaosBull on demand and gain access to all 8 resilience tools.

💻 Development & Testing

# Install dependencies
pnpm install

# Install Playwright browser
pnpm exec playwright install chromium

# Build TypeScript
pnpm run build

# Run automated smoke suite
pnpm test

📄 License

This server cannot be deployed

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Maintenance

ActivityNo data

ResponsivenessNo issues

Resources

Related MCP Connectors

aiqaramba
io.github.ajrogier
Browser-based QA for AI-built software. Test pages with real browsers via agents.
Testing & QA Tools Browser Automation Agent Orchestration
2
https://mcp.aiqaramba.com/mcp
Mimiq: AI agents use your app like your users and find what breaks A
io.github.victorgulchenko
AI agents use your app like your users, in real browsers, and report what is broken or confusing.
Testing & QA Tools App Automation Product Management
221
https://mcp.mimiqai.com/mcp
agentcheck A
io.github.agentwares
Synthetic checks, nightly regression replay and model-drift alerts for AI agents
AI & Machine Learning Testing & QA Tools Monitoring
111
https://agentwares-agentcheck.vercel.app/api/mcp
TestMu AI (formerly LambdaTest)BOAuth
io.github.LambdaTest
Agentic AI quality engineering: run, debug and triage tests on real browsers and devices
Browser Automation CI/CD & DevOps Testing & QA Tools
881
https://mcp.lambdatest.com/mcp

Related MCP Servers

AI Web Tester
Browser Automation Testing & QA Tools Developer Tools
SiamAlSobari
A
license
Not graded
quality
B
maintenance
Enables AI coding agents to autonomously interact with and test web applications in a real browser, providing DOM/Accessibility tree extraction, runtime telemetry, screenshot capture, and Markdown test reports.
Updated a month ago (2026-09-24 16:45 UTC)
12 npm
1
MIT
web-ui-tester
Browser Automation Testing & QA Tools
hofmeister
A
license
A
quality
A
maintenance
Enables AI agents to rapidly drive and inspect real web pages through persistent browser sessions, using accessibility-tree snapshots and DevTools-grade diagnostics to identify and diagnose issues.
Updated a month ago (2026-09-27 19:25 UTC)
26
MIT
Playwright MCP Server
Browser Automation Testing & QA Tools Autonomous Agents
misacandrademoon
A
license
Not graded
quality
C
maintenance
Enables AI agents to perform end-to-end web testing by controlling a real browser through tools for navigation, interaction, state inspection, screenshots, and script evaluation.
Updated 2 months ago (2026-08-30 18:55 UTC)
MIT
browsertrack
Monitoring Observability Developer Tools
litepacks
F
license
Not graded
quality
B
maintenance
Enables coding agents to access local browser diagnostics—runtime errors, console logs, network failures, breadcrumbs, DOM snapshots, and screenshots—and run closed-loop verification to debug and confirm fixes.
Updated a month ago (2026-09-27 13:00 UTC)
165 npm
-

ChaosBull MCP 🐂💥

⚡ Why ChaosBull?

🛠️ The 8 ChaosBull Superpowers

1. simulate_api_failure

2. inject_latency

3. block_resources

4. simulate_network_drop

5. trigger_system_network_error

6. simulate_stateful_failure

7. inject_response_corruption

8. assert_chaos_handled

🔌 1-Minute Setup

Cursor, Claude Desktop, Antigravity & Windsurf

💻 Development & Testing

📄 License

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

AI Web Tester

web-ui-tester

Playwright MCP Server

browsertrack

1. `simulate_api_failure`

2. `inject_latency`

3. `block_resources`

4. `simulate_network_drop`

5. `trigger_system_network_error`

6. `simulate_stateful_failure`

7. `inject_response_corruption`

8. `assert_chaos_handled`