No user-submitted related servers found.
Scored across 10 tools
Most tools target clearly different things: starting a scan, cancelling one, listing workspaces, and four distinct loot extractors (findings, ports, subdomains, technologies). The one real trap is `sniper_status` (server capability report) versus `scan_status` (job polling), which sound nearly interchangeable despite being quite different operations. Descriptions do disambiguate them, so risk is moderate rather than severe.
The dominant pattern is verb_noun (cancel_scan, list_workspaces, get_findings, get_ports, grep_loot), which is readable. But the naming is not systematic: the `sniper_` prefix appears on only two of ten tools, and it is used inconsistently — `sniper_scan` is a prefixed verb while `scan_status` is an unprefixed noun — creating two competing conventions for the same scan concept.
Ten tools is well within the sweet spot and each maps to a distinct step in the scan lifecycle (check status, start, poll, cancel) or a distinct loot type. No tool looks like padding, and nothing essential appears to be split across redundant entries.
The core loop is fully covered: open with sniper_status, launch with sniper_scan, poll with scan_status, abort with cancel_scan, then enumerate workspaces and read structured loot, with grep_loot as an escape hatch for anything unstructured. Gaps are minor — no workspace deletion/cleanup, no report export or scan-history listing beyond `recent_jobs`, and no host-inventory reader beyond per-category views.