MCP Observatory
5m ago Tracked 26,550 Last 5m ago 24h 1,898
npm JavaScript analyzed 0.9.1

browser-devtools-mcp

v0.9.1
npm

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

maintainer
serkan-ozal
license
Elastic-2.0
first seen
2026-05-22
last seen
2026-08-01
releases · 30d
0
short id
risk 31/100 · heuristic grade
B low
  • capability exposure inferred + 18
  • inherited (deps) attested + 15
  • supply-chain attested + 6
  • trust mitigators mixed − 8

attested inferred mixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 1m ago · see ecosystem CVEs →

risk trajectory 3 movements
  • C · 48 → B · 31
  • C · 53 → C · 48
  • D · 65 → C · 53
capability exposure grade factor +18
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

inherited (deps) · grade factor +15

inherited via dependencies 3
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @modelcontextprotocol/sdk · 1 hop CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @modelcontextprotocol/sdk · 1 hop CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @modelcontextprotocol/sdk · 1 hop CVE-2025-66414 fixed in 1.24.0
tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

other grade factors evidence elsewhere
embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:browser-devtools-mcp/badge.svg)](https://mcpobservatory.com/servers/npm:browser-devtools-mcp/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of serkan-ozal.