io.github.husk-security/husk
Husk
Is the Husk MCP server down? Yes. It has given no valid answer since 2026-10-19: crashed on start.
Local-first defensive scanner for vulnerable dependencies, leaked secrets, and risky agent configs
crashed on start down since 2026-10-19 · probed 2026-11-14 · unchanged since 2026-10-26
MCP error -32000: Connection closed /work/node_modules/husk-sec-linux-x64/bin/husk: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by
- Run it
- npx -y husk-sec@0.1.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/husk-security/husk
- Website
- https://husk-security.dev
- Registry
- active, updated 2026-09-11 · 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.hungnguyenhtbvn-max/autron-core · crashed on start
- io.github.hunterpercival/apex · alive
- io.github.husain-zaidi/ros-mcp · no executable
- io.github.huseyinstif/klaket-mcp · alive
- Hwip io.github.hwipit/mcp-server · alive
- io.github.hxckya/pkgtruth · alive
- Cloudcraft MCP io.github.hypark5540/cloudcraft-mcp · needs network
- Discord MCP io.github.hypark5540/discord-mcp · needs env
Servers that mention husk or dependencies or vulnerable.
- connect io.github.husk-security/connect · no DNS
- ai.smithery/STUzhy-py_execute_mcp · needs auth
- RepoPilot app.repopilot/repopilot · not found
- app.vercel.exploitwatch-kappa/exploitwatch · alive
- YAPL app.yapl/yapl · needs auth
- DefaultRank com.defaultrank/mcp · alive
- Feldspar free repository security scan com.project-feldspar/scan · alive
- Componecat com.shaftware/componecat · needs auth
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-19, in every probe since then.
- The process exited on start before it answered initialize. The error output is above.