Blitz Strike
MCP ServerA penetration-testing methodology delivered as one MCP server: BLITZ maps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE live-verifies every finding before it is reported.
- mcp-server
- security
- pentest
- methodology
Official Chrome DevTools MCP server — performance tracing, network inspection, and live debugging for coding agents.
The Google Chrome DevTools team's official MCP server gives agents direct access to browser debugging: performance trace analysis, network request inspection, console messages, screenshots, and DOM access, driven through a real Chrome instance. The de-facto choice when Claude Code (or any MCP client) needs to see why a page is slow or broken — a debugging focus that complements Playwright MCP's automation focus.
When an agent-built page is slow, throwing console errors, or behaving differently across devices — hand the agent Chrome DevTools instead of guessing from code. Pair with Playwright MCP: Playwright drives flows, Chrome DevTools explains what happened.
claude mcp add chrome-devtools -- npx chrome-devtools-mcp@latest Requires Chrome; the server launches and drives a local instance. Tool examples: performance_start_trace, network_request_from_url, take_screenshot.
Debugging-focused, not an automation harness — for multi-step flows and form filling use Playwright MCP. It drives a real browser instance, so avoid pointing it at accounts you don't want touched.
Repository
ChromeDevTools/chrome-devtools-mcpCharted
A penetration-testing methodology delivered as one MCP server: BLITZ maps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE live-verifies every finding before it is reported.
Red Hat's "ripgrep for AI context" — a C++23 zero-dependency CLI that also speaks MCP.
One shared session memory for 25+ coding agents — Claude Code, Codex, and Cursor finally remember the same project.