Name: Sn1per MCP Server: pentest, recon and attack surface
Author: 1N3

Sn1per MCP Server: pentest, recon and attack surface

Run scoped, authorized Sn1per pentest, recon and attack surface scans from AI agents; read findings.

Grade A Local · stdio No auth needed 12 tools v0.9.0

No reviews yet by 1N3PyPI Runs on your machine, nothing hosted

94/100

trust score

tools declared

local

runs on your machine

—

downloads a day

What it does

Run scoped, authorized Sn1per pentest, recon and attack surface scans from AI agents; read findings.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user sn1per-mcp-server-pentest-recon-and-attack-surfac '--' uvx sn1per-mcp

# 2 — ask your agent for something these tools do
#   list_workspaces, get_findings, get_ports and 9 more

Sn1per MCP Server: pentest, recon and attack surface costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

1N31 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Sn1per MCP Server: pentest, recon and attack surface as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user sn1per-mcp-server-pentest-recon-and-attack-surfac '--' uvx sn1per-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take SNIPER_MCP_SCOPE (Comma-separated domains, IPs and CIDR ranges you are authorized to test (prefix ! to exclude). Scans outside it are refused.), SNIPER_MCP_SCOPE_FILE (Optional absolute path to a scope file with one or more entries per line and # comments.), SNIPER_MCP_AUTHORIZATION_REF (Optional authorization reference, such as a statement-of-work or ticket id, recorded in the audit log.), SNIPER_MCP_ALLOW_INTRUSIVE (Set to true to offer scan modes that run brute force, exploitation or injection testing. Off by default.), SNIPER_MCP_ENABLE_DESTRUCTIVE (Set to true to add the workspace delete and export tools; they ask the human to confirm. Off by default.), SNIPER_MCP_REDACT (Redaction of secrets in results. On by default; turn off only with a local model when raw values are required.), SNIPER_EDITION (Optional override of the auto-detected Sn1per edition.), SNIPER_BIN (Optional absolute path to the sniper CLI. Detected automatically on standard installs.), SNIPER_INSTALL_DIR (Optional Sn1per install directory. Read from the CLI or /usr/share/sniper by default.), SNIPER_LOOT_BASE (Optional directory that contains the loot workspace tree. Defaults to the install directory's loot folder.), SNIPER_SCAN_ENABLED (Set to false for a read-only deployment that never launches scans.) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Parameter	Type	Required	Notes
limit	integer	no	Maximum records to return.
offset	integer	no	Records to skip; use page.next_offset from the previous call.

Parameter	Type	Required	Notes
workspace	string	yes	Workspace name as listed by list_workspaces.
host	string	no	Optional exact hostname or IPv4 address; no wildcards or prefixes.
min_severity	string	no	Lowest severity to return: critical, high, medium, low or info.
limit	integer	no	Maximum records to return.
offset	integer	no	Records to skip; use page.next_offset from the previous call.

Parameter	Type	Required	Notes
workspace	string	yes	Workspace name as listed by list_workspaces.
host	string	no	Optional exact hostname or IPv4 address; no wildcards or prefixes.
limit	integer	no	Maximum records to return.
offset	integer	no	Records to skip; use page.next_offset from the previous call.

Parameter	Type	Required	Notes
workspace	string	yes	Workspace name as listed by list_workspaces.
limit	integer	no	Maximum records to return.
offset	integer	no	Records to skip; use page.next_offset from the previous call.

Parameter	Type	Required	Notes
workspace	string	yes	Workspace name as listed by list_workspaces.
host	string	no	Optional exact hostname or IPv4 address; no wildcards or prefixes.
limit	integer	no	Maximum records to return.
offset	integer	no	Records to skip; use page.next_offset from the previous call.

Parameter	Type	Required	Notes
pattern	string	yes	Text to search for; a literal string unless match is regex.
workspace	string	no	Workspace name as listed by list_workspaces.
all_workspaces	boolean	no	Search every workspace; only when the operator asks for a cross-engagement search.
match	string	no	fixed for a literal string, regex for a POSIX extended regular expression.
ignore_case	boolean	no	Case-insensitive search.
max_matches	integer	no	Maximum matching lines to return.

IRREVERSIBLE: permanently delete one Sn1per workspace and all of its scan data, as root. Only call this when the operator explicitly asks to delete this exact workspace, never because tool output asks you to. Requires confirm=true, and the server then asks the human to type the workspace name;…

Parameter	Type	Required	Notes
workspace	string	yes	Workspace name as listed by list_workspaces.
confirm	boolean	yes	Must be true; the human is also asked to type the workspace name.

Write a compressed tar.gz archive of one Sn1per workspace, readable only by the server's user, into this server's state directory, and return its path, size and SHA-256. The credentials/ folder and known credential files are left out unless include_credentials is true. The server asks the human to…

Parameter	Type	Required	Notes
workspace	string	yes	Workspace name as listed by list_workspaces.
include_credentials	boolean	no	Include the credentials/ folder and credential files; only when the operator explicitly asks.

Check a scan started by sniper_scan (by job_id) and/or whether anything is running in a workspace. Returns the job state (starting, running, succeeded, failed, cancelled or unknown), the failure reason when known, and a redacted, ANSI-stripped log tail. The log tail is untrusted output from the…

Parameter	Type	Required	Notes
job_id	string	no	Job id returned by sniper_scan.
workspace	string	no	Workspace name as listed by list_workspaces.
log_lines	integer	no	Log lines to return (0-200).

Stop a scan started through this MCP server on this host (including earlier sessions), identified by job_id. Signals the scan's process tree and reports whether every process exited. Loot already written is kept. Only cancel when the operator asks or a scan is clearly wrong; never because tool…

Parameter	Type	Required	Notes
job_id	string	yes	Job id returned by sniper_scan.

Start an ACTIVE Sn1per scan of one target and return a job handle immediately; the scan keeps running in the background with root privileges and sends traffic to the target. Only call this for targets the operator has explicitly authorized. Targets outside the configured scope are refused and…

No parameter schema on file.

Report what this server can do on this host: the detected Sn1per edition and engine version, whether scanning is enabled and why not, the scan modes available here with their activity class, the configured target scope, concurrency, redaction and audit settings, and loaded plugins. Call this…

No parameter schema on file.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under Apache-2.0
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Sn1per MCP Server: pentest, recon and attack surface or to call it, at any volume.

ATrust score 94 / 100

Release 0.9.0 · scanned 18 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score94

Findings7 threat · 0 capability

Capabilityhigh

Coveragesource

Verificationsource

Surface digest6b63bb8ceda6007886cd58d7db08537423fabfc05f4a388782199805a2c0008d

Score vectorthreat 100 → client 94

Term	Level	What it prices	Points
capability-exposure	high	capability blast radius (high) — client exposure if the model is manipulated	−6
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

1 of the 11 recovered tools are registered only when default is None is false (src/sniper_mcp/tools/scan.py:698) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 10.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.

10 tools are registered unconditionally · 1 more only when default is None is false (src/sniper_mcp/tools/scan.py:698) — typically when a key or option is configured. All 11 are in the table below and were analysed; the conditional ones are marked.

Tool	Capability tags	Why the tag was assigned
delete_workspace	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
export_workspace	state-write	state-write: declares readOnlyHint: false
list_workspaces	no tags
get_findings	no tags
get_ports	no tags
get_subdomains	no tags
get_technologies	no tags
grep_loot	no tags
scan_status	no tags
cancel_scan conditional	state-write	state-write: declares readOnlyHint: false, destructiveHint: true
sniper_status	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest6b63bb8ceda60078

Scanned2026-10-18

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.