2 findingsStatic scanned
Adds Storybook component and story documentation tools to an MCP server you run yourself.
9.4M installs/moMIT
Blitzstrike
shinthink · MCP server
Point this at your source code or a live website and it runs a security audit in three stages: it enumerates the attack surface, traces how input reaches sensitive code paths, then checks each finding live before it goes into a report rather than treating a pattern match as confirmed. Source analysis covers PHP, JavaScript, Python, Java and Rust. One call drives the whole engagement, backed by a catalogue of 130 security tools with manuals, and playbooks for areas such as web application, API and active directory security.
Written by ooruby from the README of blitzstrike 2.4.145.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
It replaces a list of unverified scan hits with findings that have been checked live, each with the relevant tool manual attached.
What you could do with it
- Ask it to audit a local source folder and trace which inputs reach sensitive functions.
- Point it at a website address to run a live check on each finding before it is reported.
- Look up a specific security tool's command and flags from its catalogue before running it.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (CHANGELOG.md:822)
- node child_process (CHANGELOG.md:886)
- synchronous shell execution (CHANGELOG.md:1662)
- synchronous shell execution (CHANGELOG.md:1665)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Blitz Strike — a universal MCP security-audit toolbelt. BLITZ sweeps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE verifies live. 57 attack chains, 130-tool catalog, intelligence data layer. One server, every agent.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 2.4.145, the file with digest sha512-4qkxgSlLAzyBv/ydUI4pp+WCMW6FMDguAB4Hy/S/PhbhSZShcmmhrpsvFhpMgJ5KV9NcWIat+ipIDuHwNuHdCA==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"blitzstrike": {
"command": "npx",
"args": [
"-y",
"blitzstrike@2.4.145"
]
}
}
}Or run it directly.
npx -y blitzstrike@2.4.145Pinned to 2.4.145, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- blitzstrike
- Version read
- 2.4.145
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/blitzstrike)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.