A
licenseC
qualityB
maintenanceSecurity-focused Firefox browser MCP server for penetration testing, built on Playwright, enabling vulnerability scanning, session manipulation, network inspection, and reconnaissance.
40
1
MIT
Shade Browser Security MCP
by Atlas-X-AI
Related Servers
Alternatives to Shade Browser Security MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides structured control of a Playwright browser for QA, scraping, diagnostics, and reproducible browser workflows.4,622 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.-
- AlicenseAqualityCmaintenanceAn MCP server that runs concurrent, session-isolated Playwright browser contexts, so many agents can each drive their own browser at the same time without colliding.233 npm3MIT
- AlicenseNot gradedqualityDmaintenanceSecurity-hardened MCP server that gives AI assistants full control over your real browser session, supporting 36 tools for navigation, data extraction, monitoring, and more.MIT
- FlicenseBqualityDmaintenanceAn MCP server for generic browser automation using Playwright. Enables MCP clients to navigate pages, inspect elements, execute JavaScript, capture screenshots, and monitor console logs and network traffic via a headless Chromium instance.7-
TDQS
B3/5.0
Scored across 18 tools
Disambiguation3/5
Most tools have clear distinct purposes, but there is overlap among the network monitoring tools (browser_network_requests vs browser_network_intercept vs browser_ws_monitor) and the three browser_use_* variants (tor, tunnel, residential) are similar except for the network path. Descriptions help but an agent may struggle to pick the exact right tool in ambiguous situations.
Naming Consistency3/5
All tools are snake_case and most start with 'browser_', but the pattern after the prefix is inconsistent: some use verb_noun (use_tor, solve_challenge), some are noun phrases (network_requests, passive_recon), and one (form_scan) lacks the browser_ prefix. This mixed convention is still readable but not uniform.
Tool Count4/5
18 tools is slightly above the ideal 3-15 range but still manageable for a comprehensive security toolset. Each tool addresses a distinct aspect of browser security and anti-detection, so the count feels justified rather than bloated.
Completeness2/5
The toolset focuses heavily on network routing, monitoring, and stealth features, but omits basic browser lifecycle operations like navigate, screenshot, or close slot. Without a direct way to navigate to a URL (except via raw CDP), the surface is incomplete for practical security testing workflows.
Maintenance
ActivitySlowing
ResponsivenessNo issues