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 interactive debugger for MCP servers — list tools, call them, and inspect JSON-RPC frames.
MCP Inspector is the official reference debugging tool for MCP servers. It launches a local web UI that lets you list tools, call them with arbitrary inputs, inspect JSON-RPC frames, and watch protocol-level exchanges in real time. Essential for any server author. The npm package was renamed to @modelcontextprotocol/inspector; the slug 'mcp-cli' is kept for backward compatibility.
Best for any MCP server author iterating on tools, any Host author debugging transport negotiation, and anyone investigating a client-reported 'tool doesn't work' bug. Less suited for load testing or production traffic monitoring.
npx @modelcontextprotocol/inspector@latest Then point it at your server: select stdio transport, paste your server command (e.g. node ./server.js or python -m my_server).
Inspector runs locally — it doesn't validate how a remote Host behaves. For Host-side debugging, capture the Host's --debug log and compare against what Inspector sees.
Repository
modelcontextprotocol/inspectorCharted
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.