MCP100 verdict
Recommended for browser debugging and performance investigation when Chrome runs with an isolated, non-sensitive profile.
MCP100 Assessment
Editorial verdict
Recommended for browser debugging and performance investigation when Chrome runs with an isolated, non-sensitive profile.
Reviewed 2026-08-11 · Next review 2026-09-10
Task Fit
Mapped
Specialized workflows
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Inspecting pages, console and network activity, automating browser actions, and collecting performance evidence in Chrome
Not ideal for
- API-only testing or browsers outside the project's documented Chrome support
Avoid if
- The controlled browser contains personal accounts, secrets, or sessions that the MCP client must not inspect or modify
Trade-offs
- Deep DevTools access improves debugging, but exposes browser content and state; usage statistics and CrUX URL lookups are enabled by default unless disabled.
Evidence scope
Evidence
Popularity
49.2k MCP repository stars
7.5M package downloads
Stars observed 2026-08-14T18:46:26.000Z · Downloads observed 2026-08-14T18:46:26.000Z
Exact implementation repository metric.
Exact implementation package metric.
Maintenance
Publisher activity observed 2026-08-14T14:36:58Z
Current source snapshot
Trust review
Source relationship: Community implementation
Reviewed 2026-08-11 · Next review 2026-09-10