io.github.RCOLKITT/vaspera-hardening
io.github.RCOLKITT/vaspera-hardening
Is the io.github.RCOLKITT/vaspera-hardening MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Enterprise certification for codebases with multi-agent security, reliability, and quality audits
not found down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y vaspera-hardening-mcp-server@1.0.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/RCOLKITT/hardening-mcp
- Registry
- active, updated 2026-04-13 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.QuestLaw/questlaw-library · alive
- io.github.R1ghtHereWaiting/engagelab-email · needs env
- Reins io.github.R2Rlabs/hyperliquid-reins · needs env
- Reins io.github.R2Rlabs/reins · needs env
- io.github.RCOLKITT/vaspera-pm · not found
- io.github.RCOLKITT/vasperamemory · crashed on start
- io.github.RCS-kz/bitrix24-mcp · crashed on start
- io.github.RCS-kz/mcp-1c · crashed on start
Servers that mention hardening.
- io.github.CSOAI-ORG/meok-mcp-hardening-mcp · not found
- io.github.jmshinhwa/container-hardening-800-190 · alive
- MCP Server Attestation io.studiomeyer/server-attestation · alive
- io.github.kastelldev/kastell · timeout
- io.github.denial-web/agent-immune · crashed on start
- io.github.HMAKT99/reashield · crashed on start
- BIP Skills MCP io.github.2fizzle/bip-skills-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.