# io.github.vola-trebla/playwright-network-chaos-mcp (npm · playwright-network-chaos-mcp)

MCP server that gives AI agents dynamic network chaos control over Playwright browser sessions

- Trust score: 67/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `playwright-network-chaos-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/vola-trebla-playwright-network-chaos-mcp/playwright-network-chaos-mcp.md), [page](https://verifymcp.io/servers/vola-trebla-playwright-network-chaos-mcp/playwright-network-chaos-mcp)

## Channel facts

- Registry: `npm`
- Package: `playwright-network-chaos-mcp`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 75 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1583 tokens (~197/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add vola-trebla-playwright-network-chaos-mcp -- npx -y playwright-network-chaos-mcp
```

### Codex

```bash
codex mcp add vola-trebla-playwright-network-chaos-mcp -- npx -y playwright-network-chaos-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vola-trebla-playwright-network-chaos-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "playwright-network-chaos-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vola-trebla-playwright-network-chaos-mcp --command npx --arg -y --arg playwright-network-chaos-mcp
```

### Hermes

```yaml
mcp_servers:
  vola-trebla-playwright-network-chaos-mcp:
    command: "npx"
    args: ["-y", "playwright-network-chaos-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "vola-trebla-playwright-network-chaos-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-network-chaos-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +15)

- [security regression] Install scripts: pass → unverified
- [security regression] Provenance: fail → unverified
- [security regression] Known CVEs: partial → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Maintenance: pass → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] License: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] Licence: MIT

### 2026-07-31 (score 52, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 48, −30)

- [security regression] Known CVEs: partial → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: partial → unverified

### 2026-07-29 (score 78, +52)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-07-28 (score 26, −17)

- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 43)

First indexed and scored.

## MCP tools (8)

### `simulate_api_failure` (~197 tokens)

Intercepts API requests matching a URL pattern and makes them return an error status code. Navigates to the page and checks if a fallback UI element appears. Use to answer: does the app show a proper error state when the payment API returns 503?

Input parameters:

- `fallback_selector` (string): CSS selector for the fallback UI that should appear (e.g., '.error-boundary')
- `intercept_pattern` (string, required): Glob pattern for requests to intercept (e.g., '**/api/payment**')
- `response_body` (string): Response body to return for intercepted requests
- `status_code` (integer): HTTP error status code to return (default: 503)
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)
- `wait_ms` (integer): Milliseconds to wait after navigation before checking the fallback (default: 2000)

### `inject_latency` (~170 tokens)

Adds artificial delay to requests matching a URL pattern, simulating slow networks or overloaded APIs. Use to answer: does the app show loading states when the API takes 3 seconds? Does it time out gracefully?

Input parameters:

- `intercept_pattern` (string, required): Glob pattern for requests to delay (e.g., '**/api/**')
- `jitter_ms` (integer): Random additional delay in milliseconds (default: 0)
- `latency_ms` (integer): Base delay in milliseconds to add to each matched request (default: 3000)
- `loading_selector` (string): CSS selector for the loading state that should appear (e.g., '.skeleton-loader')
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)

### `block_resources` (~160 tokens)

Blocks requests to specified URL patterns — useful for simulating third-party outages (analytics, CDNs, tracking). Use to answer: does the app still load and function if Google Analytics or a CDN is down?

Input parameters:

- `block_patterns` (array, required): Glob patterns for requests to block (e.g., ['**/analytics**', '*.doubleclick.net/**'])
- `core_content_selector` (string): CSS selector for core content that must still be present (e.g., '.main-content')
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)
- `wait_ms` (integer): Milliseconds to wait after navigation before checking core content (default: 2000)

### `simulate_network_drop` (~179 tokens)

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?

Input parameters:

- `drop_after_ms` (integer): Milliseconds to wait before aborting the request, simulating mid-flight drop (default: 500)
- `fallback_selector` (string): CSS selector for the fallback UI that should appear (e.g., '.timeout-error')
- `intercept_pattern` (string, required): Glob pattern for requests to drop (e.g., '**/api/order**')
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)
- `wait_ms` (integer): Milliseconds to wait after navigation before checking fallback (default: 2000)

### `trigger_system_network_error` (~202 tokens)

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?

Input parameters:

- `error_code` (string, required): System network error code: addressunreachable (DNS/routing failure), connectionaborted (mid-flight drop), accessdenied (firewall/OS block), aborted (generic abort)
- `fallback_selector` (string): CSS selector for the fallback UI that should appear (e.g., '.network-error')
- `intercept_pattern` (string, required): Glob pattern for requests to abort (e.g., '**/api/payment**')
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)
- `wait_ms` (integer): Milliseconds to wait after navigation before checking fallback (default: 2000)

### `simulate_stateful_failure` (~233 tokens)

Intercepts requests matching a URL pattern and 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?

Input parameters:

- `failure_count` (integer): Number of requests to fail before allowing success (default: 3)
- `fallback_selector` (string): CSS selector for the fallback/retry UI that should appear (e.g., '.retry-button')
- `http_status` (integer): HTTP error status code for the failing requests (default: 503)
- `intercept_pattern` (string, required): Glob pattern for requests to intercept (e.g., '**/api/data**')
- `success_payload` (string): Response body for requests after the failure window (default: {"ok":true})
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)
- `wait_ms` (integer): Milliseconds to wait after navigation before checking state (default: 2000)

### `inject_response_corruption` (~226 tokens)

Intercepts requests matching a URL pattern and returns a malformed or corrupted response, simulating partial network failures at the protocol level. Use to answer: does the app handle malformed JSON, content-length lies, or truncated payloads without crashing?

Input parameters:

- `corruption_type` (string, required): Type of corruption: malformed_json (unterminated JSON body), length_mismatch (content-length claims 99999 bytes but body is short), truncated (body cut off at truncate_at_byte)
- `fallback_selector` (string): CSS selector for the fallback UI that should appear (e.g., '.parse-error')
- `intercept_pattern` (string, required): Glob pattern for requests to corrupt (e.g., '**/api/data**')
- `truncate_at_byte` (integer): Byte offset to truncate at (only used when corruption_type is truncated)
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)
- `wait_ms` (integer): Milliseconds to wait after navigation before checking state (default: 2000)

### `assert_chaos_handled` (~216 tokens)

Injects a chaos HTTP status into all matching requests, then returns a structured verdict: did the app show a fallback UI, were there unhandled JS exceptions, and did it survive? Use to answer: is the app chaos-resilient — does it show a recovery UI without throwing exceptions?

Input parameters:

- `expected_fallback_selector` (string): CSS selector for the fallback/error UI expected to appear (e.g., '.error-boundary'). chaos_survived is true only when this is found AND there are no unhandled exceptions.
- `http_status` (integer): HTTP error status to return for all matching requests (default: 500)
- `intercept_pattern` (string, required): Glob pattern for requests to fail (e.g., '**/api/**')
- `url` (string, required): URL of the page to test
- `viewport` (object): Viewport size (default: 1280×720)
- `wait_ms` (integer): Milliseconds to wait after navigation before evaluating verdict (default: 2000)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vola-trebla-playwright-network-chaos-mcp/playwright-network-chaos-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 52
- 2026-07-31: 52
- 2026-07-30: 48
- 2026-07-29: 78
- 2026-07-28: 26
- 2026-07-27: 43

## Links

- npm package: https://www.npmjs.com/package/playwright-network-chaos-mcp
- Socket report: https://socket.dev/npm/package/playwright-network-chaos-mcp
- Repository: https://github.com/vola-trebla/playwright-network-chaos-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vola-trebla-playwright-network-chaos-mcp/playwright-network-chaos-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vola-trebla-playwright-network-chaos-mcp/playwright-network-chaos-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vola-trebla-playwright-network-chaos-mcp/playwright-network-chaos-mcp