io.github.serkan-ozal/browser-devtools-mcp
NPM · BROWSER-DEVTOOLS-MCP · 2 COMPONENTS · SCANNED SEP 21
Playwright browser & Node.js MCP. ARIA refs, screenshots, ref-based interactions.
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 Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects sharp 0.34.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- 67 of 246 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8731 tokens (~171/item across 51 items; 51 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "debug_remove-probe" implies "remove" 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 52 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 io.github.serkan-ozal/browser-devtools-mcp server?
io.github.serkan-ozal/browser-devtools-mcp runs locally as an npm package, launched with npx -y browser-devtools-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · browser-devtools-mcp
claude mcp add serkan-ozal-browser-devtools-mcp -- npx -y browser-devtools-mcp
{
"mcpServers": {
"serkan-ozal-browser-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"browser-devtools-mcp"
]
}
}
} {
"servers": {
"serkan-ozal-browser-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"browser-devtools-mcp"
]
}
}
} codex mcp add serkan-ozal-browser-devtools-mcp -- npx -y browser-devtools-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"serkan-ozal-browser-devtools-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"browser-devtools-mcp"
],
"enabled": true
}
}
} openclaw mcp add serkan-ozal-browser-devtools-mcp --command npx --arg -y --arg browser-devtools-mcp
mcp_servers:
serkan-ozal-browser-devtools-mcp:
command: "npx"
args: ["-y", "browser-devtools-mcp"] {
"McpServers": {
"serkan-ozal-browser-devtools-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"browser-devtools-mcp"
]
}
}
} assistant mcp add serkan-ozal-browser-devtools-mcp -t stdio -c npx -a -y browser-devtools-mcp
{
"mcpServers": {
"serkan-ozal-browser-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"browser-devtools-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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/browser-devtools-mcp@0.9.1
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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node postinstall.cjs |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | high | yes | ||
| GHSA-rgj7-g3m4-5g8c | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 246 packages
| Packages resolved | 246 |
|---|---|
| Deprecated | 1 |
| Stale | 66 |
| 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 →
stub_intercept-http-request ~164
Installs a request interceptor stub that can modify outgoing requests before they are sent. Use cases: - A/B testing / feature flags (inject headers) - Security testing (inject malformed headers / payload) - Edge cases (special characters, large payload) - Auth simulation (add API keys / tokens in headers) Notes: - pattern is a glob matched against the full request URL (picomatch). - This modifies requests; it does not change responses. - times limits how many times the interceptor applies (-1 means infinite).
| Name | Type | Req | Description |
|---|---|---|---|
| delayMs | integer | – | – |
| modifications | object | – | Changes to apply to the request. |
| pattern | string | yes | URL glob (picomatch). |
| times | integer | – | Max applications; -1 = infinite. |
| Name | Type | Req | Description |
|---|---|---|---|
| delayMs | integer | yes | Applied artificial delay in milliseconds. |
| enabled | boolean | yes | Whether the stub is enabled. |
| kind | string | yes | Stub kind. |
| pattern | string | yes | Glob pattern. |
| stubId | string | yes | Unique id of the installed stub. |
| times | integer | yes | Max applications (-1 means infinite). |
No examples provided.
stub_list ~33
Lists currently installed stubs for the active browser context/session. Useful to debug why certain calls are being mocked/intercepted.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| stubs | array | yes | – |
No examples provided.
stub_mock-http-response ~186
Installs a response stub for matching requests using glob patterns (picomatch). Use cases: - Offline testing (return 200 with local JSON) - Error scenarios (force 500/404 or abort with timedout) - Edge cases (empty data / huge payload / special characters) - Flaky API testing (chance < 1.0) - Performance testing (delayMs) Notes: - pattern is a glob matched against the full request URL. - stubs are evaluated in insertion order; first match wins. - times limits how many times the stub applies (-1 means infinite).
| Name | Type | Req | Description |
|---|---|---|---|
| chance | number | – | Probability 0–1; omit=always. |
| delayMs | integer | – | – |
| pattern | string | yes | URL glob. |
| response | object | yes | Response. |
| times | integer | – | Max times to apply; -1=infinite. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Applied action. |
| chance | number | – | Apply probability (omit means always). |
| delayMs | integer | yes | Applied artificial delay in milliseconds. |
| enabled | boolean | yes | Whether the stub is enabled. |
| kind | string | yes | Stub kind. |
| pattern | string | yes | Glob pattern. |
| status | integer | – | HTTP status (present when action=fulfill). |
| stubId | string | yes | Unique id of the installed stub (use it to clear later). |
| times | integer | yes | Max applications (-1 means infinite). |
No examples provided.
sync_wait-for-network-idle ~133
Waits until the page is network-idle: in-flight requests <= maxConnections for at least idleTimeMs (server-side tracking, no page globals). Use before SPAs, screenshots, or AX snapshots for stable results. With long-polling, increase maxConnections or use shorter idleTimeMs.
| Name | Type | Req | Description |
|---|---|---|---|
| idleTimeMs | integer | – | Network must stay idle for this many ms to resolve. |
| maxConnections | integer | – | Idle when in-flight requests <= this. |
| pollIntervalMs | integer | – | Polling interval ms. |
| timeoutMs | integer | – | Max wait ms before failing. |
| Name | Type | Req | Description |
|---|---|---|---|
| finalInFlightRequests | integer | yes | The last observed number of in-flight requests at the moment the tool returned. |
| idleTimeMs | integer | yes | Idle duration required for success (milliseconds). |
| maxConnections | integer | yes | Idle threshold used: in-flight requests must be <= this value. |
| observedIdleMs | integer | yes | How long the in-flight request count stayed <= maxConnections right before returning (milliseconds). |
| pollIntervalMs | integer | yes | Polling interval used to sample the in-flight request count (milliseconds). |
| timeoutMs | integer | yes | Maximum allowed wait time (milliseconds). |
| waitedMs | integer | yes | Total time waited until the network became idle or the tool timed out (milliseconds). |
No examples provided.
What is the io.github.serkan-ozal/browser-devtools-mcp server?
io.github.serkan-ozal/browser-devtools-mcp is listed in the public MCP registry as io.github.serkan-ozal/browser-devtools-mcp. Playwright browser & Node.js MCP. ARIA refs, screenshots, ref-based interactions. This page covers its npm package (browser-devtools-mcp).
Is the io.github.serkan-ozal/browser-devtools-mcp server safe to use?
io.github.serkan-ozal/browser-devtools-mcp scores 66 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 September 2026. 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 io.github.serkan-ozal/browser-devtools-mcp server expose?
io.github.serkan-ozal/browser-devtools-mcp exposes 51 tools: a11y_take-aria-snapshot, a11y_take-ax-tree-snapshot, content_get-as-html, content_get-as-text, content_save-as-pdf, and 46 more. Their descriptions and schemas cost roughly 7,792 tokens of context every time the server is loaded.
Is the io.github.serkan-ozal/browser-devtools-mcp server still maintained?
io.github.serkan-ozal/browser-devtools-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.serkan-ozal/browser-devtools-mcp server under?
io.github.serkan-ozal/browser-devtools-mcp declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.