Sn1per MCP Server: pentest, recon and attack surface scanning

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

by 1N3version 0.9.0i★ –iRuns on your computer

Registry nameio.github.1N3/sn1per-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SNIPER_MCP_SCOPE, SNIPER_MCP_SCOPE_FILE, SNIPER_MCP_AUTHORIZATION_REF, SNIPER_MCP_ALLOW_INTRUSIVE, SNIPER_MCP_ENABLE_DESTRUCTIVE, SNIPER_MCP_REDACT, SNIPER_EDITION, SNIPER_BIN, SNIPER_INSTALL_DIR, SNIPER_LOOT_BASE, SNIPER_SCAN_ENABLED

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sn1per": {
      "command": "uvx",
      "args": [
        "sn1per-mcp"
      ],
      "env": {
        "SNIPER_MCP_SCOPE": "your-value",
        "SNIPER_MCP_SCOPE_FILE": "your-value",
        "SNIPER_MCP_AUTHORIZATION_REF": "your-value",
        "SNIPER_MCP_ALLOW_INTRUSIVE": "your-value",
        "SNIPER_MCP_ENABLE_DESTRUCTIVE": "your-value",
        "SNIPER_MCP_REDACT": "your-value",
        "SNIPER_EDITION": "your-value",
        "SNIPER_BIN": "your-value",
        "SNIPER_INSTALL_DIR": "your-value",
        "SNIPER_LOOT_BASE": "your-value",
        "SNIPER_SCAN_ENABLED": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sn1per --env SNIPER_MCP_SCOPE=your-value --env SNIPER_MCP_SCOPE_FILE=your-value --env SNIPER_MCP_AUTHORIZATION_REF=your-value --env SNIPER_MCP_ALLOW_INTRUSIVE=your-value --env SNIPER_MCP_ENABLE_DESTRUCTIVE=your-value --env SNIPER_MCP_REDACT=your-value --env SNIPER_EDITION=your-value --env SNIPER_BIN=your-value --env SNIPER_INSTALL_DIR=your-value --env SNIPER_LOOT_BASE=your-value --env SNIPER_SCAN_ENABLED=your-value -- uvx sn1per-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sn1per": {
      "command": "uvx",
      "args": [
        "sn1per-mcp"
      ],
      "env": {
        "SNIPER_MCP_SCOPE": "your-value",
        "SNIPER_MCP_SCOPE_FILE": "your-value",
        "SNIPER_MCP_AUTHORIZATION_REF": "your-value",
        "SNIPER_MCP_ALLOW_INTRUSIVE": "your-value",
        "SNIPER_MCP_ENABLE_DESTRUCTIVE": "your-value",
        "SNIPER_MCP_REDACT": "your-value",
        "SNIPER_EDITION": "your-value",
        "SNIPER_BIN": "your-value",
        "SNIPER_INSTALL_DIR": "your-value",
        "SNIPER_LOOT_BASE": "your-value",
        "SNIPER_SCAN_ENABLED": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sn1per": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "sn1per-mcp"
      ],
      "env": {
        "SNIPER_MCP_SCOPE": "your-value",
        "SNIPER_MCP_SCOPE_FILE": "your-value",
        "SNIPER_MCP_AUTHORIZATION_REF": "your-value",
        "SNIPER_MCP_ALLOW_INTRUSIVE": "your-value",
        "SNIPER_MCP_ENABLE_DESTRUCTIVE": "your-value",
        "SNIPER_MCP_REDACT": "your-value",
        "SNIPER_EDITION": "your-value",
        "SNIPER_BIN": "your-value",
        "SNIPER_INSTALL_DIR": "your-value",
        "SNIPER_LOOT_BASE": "your-value",
        "SNIPER_SCAN_ENABLED": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account 1N3, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Cybersecurityi

More stars than 0% of the other 996 servers in this category
Published to the registry more recently than 66% of the other 996 servers in this category
Basic checks equal to or better than 100% of the other 996 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sn1per MCP Server: pentest, recon and attack surface scanning safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.0) reached the registry 21 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Action1 MCP by usefulapi, QNSQY, EchelonGraph CVE & Exposure

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Action1 MCP by usefulapi

by m190

Read endpoints, missing updates, CVE vulnerabilities, installed software and reports in Action1.

Runs in the cloudUpdated today

Install

QNSQY

by quantumsequrity

Linux only, local: post-quantum CBOM scan, encrypt to public keys, verify. Takes no secrets

Runs on your computerUpdated today

Install

EchelonGraph CVE & Exposure

by echelongraph

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Sn1per MCP Server

Drive your self-hosted Sn1per from your AI assistant: scoped, audited, for authorized testing.

For authorized security testing only. Use the Sn1per MCP Server only against systems you own or are explicitly permitted, in writing, to test, and within the scope of that permission.

Status: beta (0.9.x). Tool names, parameters and output fields follow the compatibility promise for 0.x releases.

What it does

Sn1per MCP Server connects the AI assistant you already use to the Sn1per installation on your own Linux host. It runs locally over stdio beside Sn1per, refuses scan requests for targets outside the scope you configure (see the limits), records every scan, cancel, delete and export request it acts on in a local audit log, and returns Sn1per's findings, open ports, subdomains and technologies as structured data with secrets redacted by default. It supports Sn1per Community Edition 9.x and the 11.x engine used by SE, Professional and Enterprise; the edition matrix lists what has been verified. It is free and open source under the Apache-2.0 license, and is intended for authorized security testing only.

The server runs beside Sn1per on your host: loot stays there, and tool results leave the host only through your MCP client and the model service it uses. Read Data handling and privacy for what does leave the host.

Sn1per does the scanning. The Sn1per MCP Server lets the AI assistant you already use drive it. Generic tool-runner MCP servers expose individual commands. The Sn1per MCP Server drives Sn1per's orchestrated scan modes and returns its structured results, with scope enforcement and an audit log.

What it is not

It is not a scanner by itself. It launches and reads the Sn1per installation that is already on your host.
It does not include Sn1per. Install Sn1per first (Sn1per Community Edition, or the Professional or Enterprise installer from your licence).
It is not for shared multi-user hosts. Run it on a dedicated, single-user scanning VM or container.

Requirements

A Linux host with Sn1per Community Edition 9.x or the 11.x engine (Sn1per SE, Sn1per Professional or Sn1per Enterprise).
Python 3.11 or later. Ubuntu 22.04 and Kali 2022.x ship Python 3.10 and need a uv-managed Python (install guide).
Root, or a passwordless sudo rule for the Sn1per CLI. That rule is equivalent to full root access for the user it names; read the security model before you add it.
An MCP client that runs local stdio servers. Web, mobile and remote-connector clients are not supported in 0.9.0 (stdio only).

Quick start

Replace with the user who runs your MCP client. The env file is the canonical configuration, so --check sees exactly what the client will run.

Install pipx, then install the server as that user (never run pipx with sudo):

   sudo apt install pipx

pipx ensurepath

open a new shell, then:

pipx install sn1per-mcp==0.9.0

Create the env file /home/ /.config/sn1per-mcp/env with mode 0600:

   mkdir -p /home/<user>/.config/sn1per-mcp

install -m 0600 /dev/null /home/ /.config/sn1per-mcp/env

Put this line in it, then replace the placeholder with the targets you are authorized to test. The placeholder itself is refused (scope_invalid), so nothing is scanned until you do.

   SNIPER_MCP_SCOPE=<authorized-targets>

Check the configuration. The output includes the realpath of the Sn1per CLI that the sudo rule must name:

   /home/<user>/.local/bin/sn1per-mcp --env-file /home/<user>/.config/sn1per-mcp/env --check

Add the sudoers drop-in with that realpath (/usr/share/sniper/sniper on a standard install). Skip this step if the client runs as root. Full steps: docs/install.md.

   sudo visudo -f /etc/sudoers.d/sn1per-mcp

   <user> ALL=(root) NOPASSWD: /usr/share/sniper/sniper

   claude mcp add sn1per -s user -- /home/<user>/.local/bin/sn1per-mcp --env-file /home/<user>/.config/sn1per-mcp/env

Start a new client session and ask: "Run sniper_status".

Client setup

Only clients that passed the 0.9.0 client tests (2026-10-12) are listed. Configuration paths, approval settings and per-client notes are in docs/clients.md.

Client	Status	Delete and export tools (need MCP elicitation)
Claude Code (2.1.284)	verified	yes, in interactive sessions; `claude -p` without an SDK host cancels the confirmation, so nothing is deleted or exported
Codex CLI (0.125.0)	verified in `codex exec` only	no in `codex exec`, which declines the confirmation; the interactive Codex interface is not yet tested
Web, mobile and remote-connector clients	not supported in 0.9.0 (stdio only)	not applicable

Claude Code: the one-line command in the quick start (step 5). Codex CLI: the config.toml entry, and the approval setting that export_workspace needs there, are in docs/clients.md. Other clients that start local stdio servers are not yet tested with 0.9.0.

Is Sn1per on another machine, or is your client on macOS or Windows? See docs/remote.md for the SSH recipe (verified with a Linux OpenSSH client; Windows and macOS clients documented, unverified), WSL2 (documented, unverified) and the Docker recipes (documented, unverified).

Editions

The server detects the edition and engine from the Sn1per CLI on the host. "Verified" means exercised by the 0.9.0 verification run on 2026-10-12; "expected" means no known blocker, but not exercised. The per-tool results, the scan modes that were run and the fixes made after the run are in docs/editions.md, together with the mode tables and per-edition notes.

Edition	Engine dialect	Status
Sn1per Community Edition 9.2 (repository `master` at `a5450bc`)	9.x	verified 2026-10-12, with the server running as root
Later Sn1per Community Edition 9.x releases	9.x	expected
Sn1per SE 11.0 and 11.1	11.x	verified 2026-10-12 (11.0 as root and as a normal user through sudo, 11.1 as root)
Sn1per Enterprise, 11.3 development build	11.x	verified 2026-10-12, as a normal user through sudo
Other 11.x releases, including 11.2	11.x	expected
Sn1per Professional 2026	11.x	uses the same 11.x engine as SE and Enterprise; not yet run on a Professional install
Sn1per Community Edition below 9.2	-	not supported

Platforms: Linux only. Verified on Kali Rolling (amd64). Ubuntu 24.04: verified for the install and the MCP session (no scan was run on Ubuntu). Debian 12 and 13 and Parrot: expected. Ubuntu 22.04 and Kali 2022.x: expected only with a uv-managed Python or a separately installed Python 3.11 or later; their system Python 3.10 is refused. BlackArch: expected; needs a sniper symlink on PATH. arm64: expected. macOS and Windows are not supported as the server host; use them as the client host over SSH (docs/remote.md).

Tools

Full parameters, example results and error codes: docs/tools.md.

Tool	What it does	Read-only or changes state	Availability
`sniper_status`	Reports the detected edition, the scan modes available, the configured scope and why scanning may be unavailable	Read-only	Always
`list_workspaces`	Lists the Sn1per loot workspaces on the host	Read-only	Always
`scan_status`	Reports a scan's state and a redacted log tail, or whether anything runs in a workspace	Read-only	Always
`get_findings`	Reads findings with severity, title, location and host	Read-only	Always
`get_ports`	Reads open ports with protocol, service and version	Read-only	Always
`get_subdomains`	Reads discovered subdomains	Read-only	Always
`get_technologies`	Reads detected web technologies	Read-only	Always
`grep_loot`	Searches loot files in one workspace (or in all of them, when the operator asks) for a string or an extended regular expression	Read-only	Always
`sniper_scan`	Starts a Sn1per scan of one target, as root, and returns a job handle	Changes state: sends traffic to the target	Always registered; refuses every target until you configure a scope
`cancel_scan`	Stops a scan that this server started	Changes state	Always
`delete_workspace`	Permanently deletes one workspace and its scan data, as root, after the human types the workspace name	Changes state: irreversible	Only with `SNIPER_MCP_ENABLE_DESTRUCTIVE=1` and a client with MCP elicitation
`export_workspace`	Writes a tar.gz archive of one workspace into the server's state directory, after the human types the workspace name	Changes state: writes a file	Only with `SNIPER_MCP_ENABLE_DESTRUCTIVE=1` and a client with MCP elicitation

Configuration

All settings, the scope grammar and the command-line flags: docs/configuration.md.

Scope (required for scans): SNIPER_MCP_SCOPE and/or SNIPER_MCP_SCOPE_FILE list the domains, IPv4 and IPv6 addresses and CIDR ranges you are authorized to test, with ! exclusions. With no scope, every scan request is refused. One invalid entry makes the whole scope invalid.
Intrusive modes: modes that run credential brute force, exploitation or injection testing are off until you set SNIPER_MCP_ALLOW_INTRUSIVE=1. The default mode is stealth.
Destructive tools: delete_workspace and export_workspace exist only with SNIPER_MCP_ENABLE_DESTRUCTIVE=1, and both ask the human to type the workspace name.
Redaction: secrets in results are redacted by default (SNIPER_MCP_REDACT). Redaction is pattern-based; it is not data-loss prevention.

Security model

The server is a set of controls around a root-capable engine, not a security boundary. Read docs/security-model.md before you deploy it. In short:

The passwordless sudo rule for the Sn1per CLI is equivalent to full root access for that user.
The scope applies to the target the agent requests, at launch time. Sn1per resolves names again during the scan, may contact third-party services, and some modes scan hosts they discover. Use an egress filter on the scanning host.
These controls do not stop an agent that also has shell or file-write access as the same user. Keep the scope and env files under /etc/sn1per-mcp/, owned by root, and deny those tools for them.
Everything read from loot, logs and searches is returned as untrusted data, because scanned systems control it.

Responsible use

The Sn1per MCP Server lets

Only the beginning is shown; read the rest in the repo

Sn1per MCP Server: pentest, recon and attack surface scanning

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Cybersecurityi

Common questions

Alternatives

Action1 MCP by usefulapi

QNSQY

EchelonGraph CVE & Exposure

README from the maker

Sn1per MCP Server

What it does

What it is not

Requirements

Quick start

open a new shell, then:

Client setup

Editions

Tools

Configuration

Security model

Responsible use