com.pulsemcp/playwright-stealth
NPM · PLAYWRIGHT-STEALTH-MCP-SERVER · SCANNED SEP 20
Browser automation using Playwright with optional stealth mode to bypass anti-bot protection.
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 → Why this is hard to score →
Supply Chain Security97
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 59 of 135 dependencies flagged as unhealthy (3 deprecated). 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 97 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1312 tokens (~218/item across 6 items; 6 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 Management77
- Stability observed for 23 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "browser_execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.pulsemcp/playwright-stealth MCP server?
com.pulsemcp/playwright-stealth runs locally as an npm package, launched with npx -y playwright-stealth-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · playwright-stealth-mcp-server
claude mcp add com-pulsemcp-playwright-stealth -- npx -y playwright-stealth-mcp-server
{
"mcpServers": {
"com-pulsemcp-playwright-stealth": {
"command": "npx",
"args": [
"-y",
"playwright-stealth-mcp-server"
]
}
}
} {
"servers": {
"com-pulsemcp-playwright-stealth": {
"command": "npx",
"args": [
"-y",
"playwright-stealth-mcp-server"
]
}
}
} codex mcp add com-pulsemcp-playwright-stealth -- npx -y playwright-stealth-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pulsemcp-playwright-stealth": {
"type": "local",
"command": [
"npx",
"-y",
"playwright-stealth-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-pulsemcp-playwright-stealth --command npx --arg -y --arg playwright-stealth-mcp-server
mcp_servers:
com-pulsemcp-playwright-stealth:
command: "npx"
args: ["-y", "playwright-stealth-mcp-server"] {
"McpServers": {
"com-pulsemcp-playwright-stealth": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"playwright-stealth-mcp-server"
]
}
}
} assistant mcp add com-pulsemcp-playwright-stealth -t stdio -c npx -a -y playwright-stealth-mcp-server
{
"mcpServers": {
"com-pulsemcp-playwright-stealth": {
"command": "npx",
"args": [
"-y",
"playwright-stealth-mcp-server"
]
}
}
} 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.
- 20 Sept 26 −3
- Stability: pass → 0.77 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/playwright-stealth-mcp-server@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 135 packages
| Packages resolved | 135 |
|---|---|
| Deprecated | 3 |
| Stale | 57 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
browser_close ~35
Close the browser session. Shuts down the browser and clears all state. A new browser will be launched on the next execute call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
browser_execute ~325
Execute Playwright code in the browser. This tool runs JavaScript code with access to a Playwright `page` object. The browser session persists across calls, so you can navigate, interact with elements, and extract data across multiple tool invocations. **Available in scope:** - `page` - The Playwright Page object with full API access **Example usage:** Navigate to a page: ```javascript await page.goto('https://example.com'); return await page.title(); ``` Click an element and wait: ```javascript await page.click('button.submit'); await page.waitForSelector('.success-message'); ``` Extract text content: ```javascript const items = await page.$$eval('.item', els => els.map(el => el.textContent)); return items; ``` Fill a form: ```javascript await page.fill('input[name="email"]', 'test@example.com'); await page.fill('input[name="password"]', 'secret'); await page.click('button[type="submit"]'); ``` **Returns:** - `success`: boolean indicating if execution succeeded - `result`: JSON stringified return value (if any) - `error`: error message (if failed) - `consoleOutput`: array of console messages from the page **Note:** When STEALTH_MODE=true, the browser includes anti-detection measures to help bypass bot protection.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Playwright code to execute. The `page` object is available in scope. |
| timeout | number | – | Execution timeout in milliseconds. Default: 30000 |
No output schema declared.
No examples provided.
browser_get_state ~118
Get the current browser state. Returns information about the current browser session including the URL, page title, and whether a browser is open. **Returns:** - `currentUrl`: Current page URL - `title`: Current page title - `isOpen`: Whether a browser session is active - `stealthMode`: Whether stealth mode is enabled - `headless`: Whether running in headless mode - `proxyEnabled`: Whether a proxy is configured - `ignoreHttpsErrors`: Whether HTTPS certificate errors are being ignored
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
browser_screenshot ~481
Take a screenshot of the current page, a specific element, or a page region. Captures the visible viewport, full page, a specific element, or a rectangular region as a PNG image. Screenshots are saved to filesystem storage and can be accessed later via MCP resources. **Parameters:** - `fullPage`: Whether to capture the full scrollable page (default: false) - `selector`: CSS selector of a specific element to screenshot (e.g., '#main-content', '.hero-banner', 'table.results') - `clip`: Region of the page to screenshot as {x, y, width, height} in pixels - `resultHandling`: How to handle the result: - `saveAndReturn` (default): Saves to storage AND returns inline base64 image - `saveOnly`: Saves to storage and returns only the resource URI (more efficient for large screenshots) **Note:** `fullPage`, `selector`, and `clip` are mutually exclusive. Only one can be specified per call. **Returns:** - With `saveAndReturn`: Inline base64 PNG image data plus a resource_link to the saved file - With `saveOnly`: A resource_link with the `file://` URI to the saved screenshot **Dimension Limits:** Full-page screenshots are limited to 8000 pixels in any dimension. If a full-page screenshot would exceed this limit, it is automatically clipped from the top-left corner and a warning is included in the response. Element and clip screenshots are not subject to this limit. **Use cases:** - Verify page state after navigation - Screenshot a specific element like a chart, table, or form - Capture a region of the page by coordinates - Debug automation issues - Store screenshots for later reference via MCP resources
| Name | Type | Req | Description |
|---|---|---|---|
| clip | object | – | Region of the page to screenshot. Mutually exclusive with fullPage and selector. |
| fullPage | boolean | – | Capture the full scrollable page. Default: false |
| resultHandling | string | – | How to handle the screenshot result. 'saveAndReturn' (default) saves to storage and returns inline base64, 'saveOnly' saves to storage and returns only the resource URI |
| selector | string | – | CSS selector of a specific element to screenshot. Mutually exclusive with fullPage and clip. |
No output schema declared.
No examples provided.
browser_start_recording ~199
Start recording the browser session as a video. This tool begins capturing all browser interactions as a WebM video file. It works by recycling the browser context with video recording enabled. **Session state preservation:** Cookies and localStorage are automatically saved and restored when the context is recycled. sessionStorage for the current origin is also preserved on a best-effort basis. In rare cases involving multiple origins, some state may not be restored — if you experience authentication issues, log in again. **Behavior when already recording:** If recording is already active, the current recording will be stopped (saving the video) and a new recording will begin. **The video is NOT available until you call `browser_stop_recording`.** Playwright only finalizes the video file when the recording context is closed. **Returns:** - Confirmation that recording has started - The URL the browser was previously on (if any) — the browser navigates back to it automatically
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
browser_stop_recording ~154
Stop recording the browser session and save the video. This tool stops the active video recording, saves the video file, and returns a resource URI for the recorded video. **Session state preservation:** Cookies and localStorage are automatically saved and restored when the context is recycled. sessionStorage for the current origin is also preserved on a best-effort basis. The browser automatically navigates back to the URL it was on before the recording stopped. **Error:** Returns an error if no recording is currently active. Use `browser_start_recording` first. **Returns:** - A resource_link with the `file://` URI to the saved video file (WebM format) - The video can be accessed later via MCP resources
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.pulsemcp/playwright-stealth MCP server?
com.pulsemcp/playwright-stealth is an MCP server listed in the public MCP registry as com.pulsemcp/playwright-stealth. Browser automation using Playwright with optional stealth mode to bypass anti-bot protection. This page covers its npm package (playwright-stealth-mcp-server).
Is the com.pulsemcp/playwright-stealth MCP server safe to use?
com.pulsemcp/playwright-stealth scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.pulsemcp/playwright-stealth MCP server expose?
com.pulsemcp/playwright-stealth exposes 6 tools: browser_execute, browser_screenshot, browser_get_state, browser_close, browser_start_recording, browser_stop_recording. Their descriptions and schemas cost roughly 1,312 tokens of context every time the server is loaded.
Is the com.pulsemcp/playwright-stealth MCP server still maintained?
com.pulsemcp/playwright-stealth is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.pulsemcp/playwright-stealth MCP server under?
com.pulsemcp/playwright-stealth declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.