← Back to directory
B

Blitz Strike

Community
Recon at speed. Analysis in depth. Validation before report.
GitHub source repository ↗
★ 634 Stars Category · Dev Tools Very popular
42FMRS · D

Blitz Strike is a self-hosted MCP penetration-testing toolbelt that packages a three-tier methodology — recon, source analysis, live validation — as server-side tools, backed by a 130-tool catalog, 334 manual/playbook files, 57 escalation chains, and a substantial intelligence layer, plus a benchmark and coverage matrix (the README reports detection rate 1.0, false-positive rate 0, and 56/60 coverage pairs). Its defining stance is that a scan hit is a hypothesis and only a live test is a verdict, using marker reflection plus a negative control to suppress false positives. It is MIT-licensed and community-maintained rather than official, aimed at authorized security researchers. Users should note that live testing sends real requests and requires correct scope configuration, that ensure_tool modifies the local machine, that some datasets must be synced on demand, and that credentials are provided through environment variables.

Reliability
6/20
Security and permissions
4/20
Maintenance
9/20
Documentation
13/20
Setup experience
10/20
Read the FMRS scoring method →

Blitz Strike is a structured penetration-testing methodology delivered as a universal MCP server (TypeScript / Bun), mapping reconnaissance, source analysis, and live validation onto three callable tool tiers that run server-side. Tier 1, BLITZ, maps the attack surface: it enumerates unauthenticated entry points and dangerous sinks at scale with file:line references. Tier 2, EAGLE-EYE, performs static analysis and data-flow tracing, matching source-to-sink reachability against an escalation-chain graph. Tier 3, STRIKE, performs live validation via marker reflection plus a negative control, and enforces scope. A single run_engagement call drives scope gating, triage, chain enrichment, and findings, with the LLM automatically classifying the target (URL → live pipeline, filesystem path → source pipeline). Beyond the three tiers it ships a 130-tool catalog, 317 deep tool manuals, 17 engagement playbooks, an intelligence layer (139 WAF signatures, 89 technologies, 53 CVEs, 103 ports, 66 payload categories, ~11.9k nuclei templates, 34 attack-vector categories / 588 vectors), CVSS v3.1 scoring, dedup, reproducible reports, and a self-growing memory layer. It is intended for security researchers and teams performing authorized assessments.

Tools

blitz_scan
Scan a source tree: enumerate unauthenticated entry points and dangerous sinks with file:line references.
blitz_file
Same scan for a single file.
eagle_eye
Return a function's full body, sinks in scope, and auth gates in scope.
eagle_grep
Precision sink grep — report a hit only inside a function body, flagged guarded or un-guarded.
enrich_scan
Scan and match detected sinks to escalation chains (chains.json).
strike_verify
Live HTTP verification with marker, negative control, and baseline.
strike_resolve
Attach a live STRIKE verdict to a finding and advance its lifecycle.
scope_check
Enforce scope before active testing (no-DoS, exclusion-aware, mode-gated).
run_engagement
Full three-tier audit in one call: scope gate → triage → chain enrichment → findings.
list_chains
List all escalation chains in the data layer.
fofa_search
FOFA asset index search (requires FOFA_EMAIL and FOFA_KEY).
nvd_lookup
CVE lookup from NVD 2.0 (no key required).
live_recon
Modular passive-first recon: fingerprint, WAF/tech/version, crawler, params, subdomains, Wayback, API discovery, port scan.
tool_lookup
Look up a tool's command, flags, install, and check.
list_tools
List all catalog tools, grouped by category.
skill_lookup
Search the skills playbook knowledge base by topic.
list_skills
List all skill playbooks.
read_skill
Read the full content of a playbook.
ensure_tool
Check whether a tool is installed; if not, auto-install it.
read_tool_manual
Read a full deep manual for a tool (317+ manuals).
list_manuals
List all manuals and playbooks.
read_playbook
Read an engagement playbook (web-app, api-security, AD, etc.).
list_playbooks
List all 17 engagement playbooks.
cvss_score
Compute a deterministic CVSS v3.1 base score, vector, and severity (self-computed, not read from NVD).
dedup_findings
Collapse findings sharing a root cause (sink × source × CWE) into one group per root cause.
generate_report
Emit a reproducible markdown/JSON report with summary and SHA-256 integrity hash.
run_enterprise_benchmark
Run the labelled enterprise corpus and report detection rate, false-positive rate, and precision.
coverage_matrix
Enumerate language × sink-class coverage (4 languages × 15 sink classes) plus coverage ratio.
taint_file
Inter-procedural taint analysis (PHP) — reachable, sanitized, authorized sinks.
taint_scan
Universal taint analysis (PHP/JS/TS/Python/Java) with source→sink tracing.
taint_tree
Taint propagation tree — how a source flows to a sink.
trace_data_flow
Window-based data-flow trace with sanitizer and auth-gate awareness.
variant_analysis
Group reachable sinks into variant families.
list_languages
List supported analysis languages and extensions.
detect_waf
Detect a WAF from response headers/body (139 signatures).
tech_correlation
Correlate tech to known vulns and CVEs (89 technologies).
cve_correlation
Correlate a CVE to product, targets, and severity (53 CVEs).
port_correlation
Correlate a port to service and attack vectors (103 ports).
fuzzer_payloads
Fuzzing payloads, vulnerable patterns, and chain rules.
intel_summary
Counts of every intelligence dataset.
payload_lookup
Find exploit payloads (66 categories from PayloadsAllTheThings).
read_payload
Read a full payload collection.
template_lookup
Find nuclei detection templates (11.9k YAML signatures).
list_attack_vectors
List the full web attack-vector taxonomy (34 categories, 588 vectors).
attack_vectors
Enumerate the vector list for one category (e.g. ssrf, business logic, ai/llm).
check_update
Query the npm registry for the latest blitzstrike version.
remember
Save a reusable insight (deduped); verified=true only if the marker reflected and the negative control stayed inert.
memory_lookup
Search memory by topic/tag/content, scored.
memory_list
List all memory entries, grouped by type.
memory_forget
Remove a memory entry (append-only tombstone).
confidence_weights
Get or set the confidence-scoring weight factors.
finding_attach_evidence
Attach a redacted and hashed evidence record to a finding.

Setup

  1. Run npx -y blitzstrike doctor to verify the environment (bun/node runtime, tool catalog, FOFA credentials, data layers); every issue comes with a fix: line.
  2. Run npx -y blitzstrike install. It detects installed agent CLIs (Claude Code, Cursor, OpenCode, Codex, Hermes, Gemini, Windsurf, Copilot, Cline) and merges the Blitz Strike entry into each config in its native format without overwriting existing MCP servers; add --dry-run to preview.
  3. Restart your agent and call run_engagement.
  4. From source: git clone https://github.com/shinthink/blitzstrike.git && cd blitzstrike && bun install && bun run src/index.ts serve --mcp.
  5. Client config example: under mcpServers, set command to blitzstrike and args to ["serve", "--mcp"]
claude_desktop_config.json
{
  "mcpServers": {
    "blitzstrike": {
      "command": "blitzstrike",
      "args": ["serve", "--mcp"]
    }
  }
}

Fit and risk

Best for

  • Authorized security researchers and red/blue team engineers who want verify-before-report workflows
  • Agent users who want a full penetration-testing flow driven by one call inside an MCP client
  • Developers and security reviewers needing code audit (taint analysis, source-to-sink, variant analysis)
  • Teams that want a structured methodology plus knowledge base (manuals, playbooks, escalation chains) instead of scattered scripts

Not for

  • Anyone wanting to test external systems without explicit owner authorization
  • Anyone treating a scan hit as a confirmed vulnerability and skipping STRIKE validation
  • Users expecting everything to work offline out of the box — payloads and templates need `blitzstrike sync-data`, and fofa_search needs FOFA_EMAIL/FOFA_KEY
  • Users looking for an official or vendor-endorsed product; this is a community project

Required permissions

  • Read the source directory or files being audited
  • Run a local process over stdio (command `blitzstrike`, args `serve --mcp`)
  • Make outbound HTTP requests to the audited target for live validation and recon
  • Write to client MCP config files (install merges into existing config, never overwrites)
  • Read/write memory and data cache under ~/.blitzstrike (overridable via BLITZSTRIKE_HOME / BLITZSTRIKE_DATA)
  • Optional: FOFA_EMAIL / FOFA_KEY for FOFA access, and H1_USERNAME to add the X-HackerOne-Research header
  • ensure_tool may auto-install missing security tools on the local machine

Risks and side effects

  • Live validation and live_recon send real requests to targets; misconfigured scope or missing authorization can cause harm or legal exposure
  • ensure_tool auto-installation modifies the local environment and introduces supply/version risk
  • Payloads, nuclei templates, and exploitation manuals are offensive material that can be misused
  • Memory is stored append-only as JSONL at ~/.blitzstrike/memory.jsonl and may accumulate sensitive target data
  • FOFA and HackerOne credentials are supplied via environment variables and can leak
  • Automated scan results can still be false positives — the README insists every finding stays a hypothesis until strike_verify confirms it

Troubleshooting

  1. Run `blitzstrike doctor` first: it checks the runtime (bun/node, OK/FAIL plus a fix), the 130-tool catalog (e.g. 63/130 installed, 67 on-demand), FOFA credentials (OK/WARN), and whether data layers are present
  2. If the catalog reports missing tools, use `ensure_tool(name)` or `blitzstrike sync-data` to fetch heavy datasets such as payloads and templates
  3. Server missing in the client: confirm you ran `blitzstrike install` (or preview with `--dry-run`) and restart the agent; if no client was detected, paste the printed snippet manually
  4. fofa_search unavailable: check that FOFA_EMAIL and FOFA_KEY are set; all other tools need no credentials
  5. Unexpected data-cache or memory location: check the BLITZSTRIKE_HOME / BLITZSTRIKE_DATA environment variables
  6. Suspecting a false positive: use eagle_eye to confirm the sink is really inside the reachable scope of an unauthenticated handler, and refute with the chain's negative_control
  7. Stale version or data: run `blitzstrike update` or use check_update to query the latest npm version

Use cases

Run a full three-tier audit (BLITZ → EAGLE-EYE → STRIKE) over a source directory
Validate findings live against an authorized URL using marker reflection and a negative control to remove false positives
Match reachable sinks against the 57 escalation chains to decide whether a finding is actually exploitable
Generate reproducible reports with a SHA-256 integrity hash and compute CVSS v3.1 scores
Look up CVEs (nvd_lookup), technology-to-vulnerability correlations, port attack vectors, and exploit payloads
Re-run quality metrics via run_enterprise_benchmark and coverage_matrix

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
OpenCodeFull support
HermesFull support
GeminiFull support
WindsurfFull support
CopilotFull support
ClineFull support