Skip to main content
Glama
Sign In
ChaosBull MCP

ChaosBull MCP

by Omkar2240
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ChaosBull MCP

No user-submitted related servers found.

    Related Servers

    • Bezlo MCP Server

      gba3124
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to load web pages in true-to-size iPhone, iPad, and Android device frames, capture screenshots, inspect interactive elements and layout diagnostics, and automate tap/type/scroll flows with network mocks, console errors, and test evidence.
      MIT

    • uisight

      oStavrou014
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive live mobile and desktop browser sessions and receive measured UI findings as text — contrast ratios, touch-target sizes, overflow, and theme drift — rather than screenshot guesses. It also lets the agent navigate, tap, type, switch device/theme, read console errors, and pick up bug notes the human pinned in a shared live panel.
      268 npm
      MIT

    • Argus QA MCP

      RileyHall99
      A
      license
      A
      quality
      B
      maintenance
      Gives AI agents a real Chromium browser via Playwright to QA-test web apps, with pass/fail assertions, network mocking, recorded traces and reports, and safety guards that block live payment traffic. Test outcomes come back as explained verdicts suitable for review or email delivery.
      18
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool maps to a distinct failure mode (latency, blocked resources, connection drop, system-level network error, stateful failure, response corruption), and descriptions clarify use cases. However, simulate_api_failure and assert_chaos_handled both intercept requests, return error statuses, and check fallback UI, creating some overlap; simulate_network_drop and trigger_system_network_error also both abort requests with subtle differences.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern: simulate_api_failure, inject_latency, block_resources, trigger_system_network_error, assert_chaos_handled. The verb choices differ appropriately by action type while remaining predictable and readable.

    Tool Count5/5

    Eight tools is well-scoped for a chaos engineering server, with each tool representing a meaningful failure injection or assertion capability. No tool feels redundant enough to remove, and the set is not bloated.

    Completeness4/5

    The surface covers a broad range of browser/network chaos scenarios: API errors, latency, resource blocking, connection drops, OS-level errors, stateful failures, corruption, and a resilience assertion. Minor gaps exist, such as no tool for combined/concurrent chaos scenarios or explicit success-path verification, but core chaos workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources