F
licenseB
qualityD
maintenancePlaywright wrapper for MCP that enables LLM-powered clients to control a browser for automation tasks.
4
10
1
-
PhiShark Playwright MCP
by phishark-git
Related Servers
Alternatives to PhiShark Playwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceProvides a drop-in Playwright MCP proxy with a judgment layer that triages page states, shields against prompt injection, prunes snapshots by goal, and gates risky actions, enabling coding agents to use standard Playwright MCP tools more safely.281MIT
- AlicenseCqualityBmaintenanceSecurity-focused Firefox browser MCP server for penetration testing, built on Playwright, enabling vulnerability scanning, session manipulation, network inspection, and reconnaissance.401MIT
- AlicenseNot gradedqualityCmaintenanceDrop-in replacement for Playwright MCP that adds WebMCP support, exposing page-defined tools as gated webmcp:* tools with provenance tracking, schema-change warnings, and mandatory confirmation.2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides structured control of a Playwright browser for QA, scraping, diagnostics, and reproducible browser workflows.7,762 npmMIT
- FlicenseNot gradedqualityCmaintenanceA policy-aware Meta-MCP server that orchestrates Playwright and Chrome DevTools for secure, high-level browser automation with origin whitelists and credential redaction.-
TDQS
B3.4/5.0
Scored across 26 tools
Disambiguation4/5
Most tools have distinct purposes, but there is slight potential for confusion between 'browser_type' and 'browser_fill_form', and between 'browser_take_screenshot' and 'browser_snapshot', though descriptions clarify the differences. Overall, the set is largely well-disambiguated.
Naming Consistency5/5
All tool names follow a consistent 'browser_' or 'phishark_' prefix with verb_noun structure, ensuring predictability. The naming convention is uniform and easy to interpret.
Tool Count4/5
With 26 tools, the set is comprehensive for browser automation, covering a wide range of actions. While slightly above the typical 3-15 range, each tool serves a distinct need, making the count reasonable for the domain.
Completeness5/5
The tool surface covers nearly all standard browser automation operations including navigation, interaction, network requests, console, and accessibility, plus additional security scanning. No obvious gaps are present for the stated purpose.
Maintenance
ActivityStale
ResponsivenessNo issues