Is Browser DevTools safe and trustworthy?

tashan scores Browser DevTools on public evidence — it is currently abandoned, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time, its declared dependencies reach: browser, credentials, network. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Browser DevTools?

Don't. This capability has been discontinued by its author or publisher and is not scored or recommended. If you are already running it, `npx tashan-cli doctor` will flag it and name what to move to.

Who maintains Browser DevTools?

source: serkan-ozal/browser-devtools-mcp.

‹ The Index

Browser DevTools

npm

[DEPRECATED] This package has been renamed. Please use @ironbee-ai/devtools instead.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Browser & Web — see all ranked ›

Discontinued — do not install. The author's own notice: “[DEPRECATED] This package has been renamed. Please use @ironbee-ai/devtools instead.” It stays listed so anyone already running it can find this page, and so npx tashan-cli doctor can warn about it. It is not scored and does not appear in any ranking.

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

Adoption: 3.7k/wk
Freshness: 64.0
Health: abandoned
License: Elastic-2.0

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.9.1 — this package, not its dependency tree

Runs a script at install timecodenode postinstall.cjs

Drives a browser · Handles credentials or secrets · Makes network requestsfrom declared dependencies

Can carry remote content into your agentit can pull third-party text into the model's context — treat what it returns as untrusted input

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-10 browser-devtools-mcp now reaches browser, credentials, network Its declared dependencies reach further into your machine than they did before.
2026-08-10 browser-devtools-mcp now runs a script when it installs Install-time code executes on your machine before you have used the tool once, and it did not do this before.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 2 changes to Browser DevTools in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

npm ↗ · source ↗ · pkg:browser-devtools-mcp

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?