TUI for triaging Nessus findings: import.nessus into SQLite, launch nmap/NetExec against affected hosts, track revie...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Multiple
Fastest way to find out if cerno belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add cerno -- npx cernoRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove cernoNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ cerno ← registers here
TUI for triaging Nessus findings: import.nessus into SQLite, launch nmap/NetExec against affected hosts, track review progress across scans, and drive it all from an MCP client.
Source: GitHub repository
Source check: October 30, 2026
Upstream commit: October 30, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.