io.github.vola-trebla/playwright-network-chaos-mcp
NPM · PLAYWRIGHT-NETWORK-CHAOS-MCP · SCANNED AUG 3
MCP server that gives AI agents dynamic network chaos control over Playwright browser sessions
Available components
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. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 75 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · playwright-network-chaos-mcp
claude mcp add vola-trebla-playwright-network-chaos-mcp -- npx -y playwright-network-chaos-mcp
codex mcp add vola-trebla-playwright-network-chaos-mcp -- npx -y playwright-network-chaos-mcp
{
"$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 mcp add vola-trebla-playwright-network-chaos-mcp --command npx --arg -y --arg playwright-network-chaos-mcp
mcp_servers:
vola-trebla-playwright-network-chaos-mcp:
command: "npx"
args: ["-y", "playwright-network-chaos-mcp"] {
"mcpServers": {
"vola-trebla-playwright-network-chaos-mcp": {
"command": "npx",
"args": [
"-y",
"playwright-network-chaos-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +15
- Install scripts: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Maintenance: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- License: pass → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- Licence: MIT functional
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −30
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- 29 Jul 26 +52
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 28 Jul 26 −17
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 43
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 97 packages
97 packages in the resolved dependency tree · 95 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
assert_chaos_handled ~216
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?
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Glob pattern for requests to fail (e.g., '**/api/**') |
| url | string | yes | 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) |
No output schema declared.
No examples provided.
block_resources ~160
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?
| Name | Type | Req | Description |
|---|---|---|---|
| block_patterns | array | yes | 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 | yes | 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) |
No output schema declared.
No examples provided.
inject_latency ~170
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?
| Name | Type | Req | Description |
|---|---|---|---|
| intercept_pattern | string | yes | 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 | yes | URL of the page to test |
| viewport | object | — | Viewport size (default: 1280×720) |
No output schema declared.
No examples provided.
inject_response_corruption ~226
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?
| Name | Type | Req | Description |
|---|---|---|---|
| corruption_type | string | yes | 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 | yes | 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 | yes | 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) |
No output schema declared.
No examples provided.
simulate_api_failure ~197
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?
| Name | Type | Req | Description |
|---|---|---|---|
| fallback_selector | string | — | CSS selector for the fallback UI that should appear (e.g., '.error-boundary') |
| intercept_pattern | string | yes | 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 | yes | 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) |
No output schema declared.
No examples provided.
simulate_network_drop ~179
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?
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Glob pattern for requests to drop (e.g., '**/api/order**') |
| url | string | yes | 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) |
No output schema declared.
No examples provided.
simulate_stateful_failure ~233
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?
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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) |
No output schema declared.
No examples provided.
trigger_system_network_error ~202
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?
| Name | Type | Req | Description |
|---|---|---|---|
| error_code | string | yes | 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 | yes | Glob pattern for requests to abort (e.g., '**/api/payment**') |
| url | string | yes | 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) |
No output schema declared.
No examples provided.