Sn1per MCP Server: pentest, recon and attack surface scanning

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

von 1N3Version 0.9.0i★ –iLäuft auf deinem Computer

Name in der Registryio.github.1N3/sn1per-mcp

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

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

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Stimmen der NutzeriNoch keine BewertungenBewertungen starten in einem späteren Schritt zusammen mit Benutzerkonten
Unsere Basischecksi1 von 1 bestandenAnhand öffentlicher Informationen geprüft; Code noch nicht gescannt
NutzungiNoch nicht gemessen★ –

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

Verbindung: Läuft auf deinem Computer
Transport: stdio
Kategorie: Sonstiges

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

Basischecks: 1 von 1 bestanden
Läuft auf deinem Computer mit den Rechten deines Benutzerkontos (Dateien, Netzwerk, Apps).
Das trägst du selbst ein: 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

Du brauchst

PyPIuv für Python installiert (für den Befehl uvx)

Welche App nutzt du?

ClaudeClaude CodeCursorVS CodeChatGPT

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein

{
  "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"
      }
    }
  }
}

Führe das in deinem Terminal aus

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

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "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"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "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"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

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.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026

✓ Bestanden
Entwickler passt zum Repo
Der Registry-Name wurde mit dem GitHub-Konto 1N3 bestätigt, dem das Repo gehört
… Noch nicht geprüft
Wird noch gepflegt
Dieses Repo haben wir noch nicht von GitHub gelesen
… Noch nicht geprüft
Hat eine Lizenz
Dieses Repo haben wir noch nicht von GitHub gelesen
– Nicht zutreffend
Endpunkt antwortet
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
– Nicht zutreffend
Anmeldung mit OAuth
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
… Noch nicht geprüft
Keine versteckten Anweisungen in Tool-Beschreibungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen

Im Vergleich mit anderen in Sonstigesi

Mehr Sterne als 0 % der anderen 32709 Server in dieser Kategorie
Neuer in der Registry veröffentlicht als 65 % der anderen 32709 Server in dieser Kategorie
Basischecks gleich gut wie oder besser als bei 100 % der anderen 32709 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Sn1per MCP Server: pentest, recon and attack surface scanning sicher?

Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.9.0) kam vor 20 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv) auf deinem Computer.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, SwarmMemo

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Spec Driven Development

von formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Läuft auf deinem Computer★ 440MITAktualisiert vor 14 Monaten

Installieren

Remote Desktop Commander

von desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Läuft in der Cloud★ 211Aktualisiert vorgestern

Installieren

SwarmMemo

von Hugo0

Talk with agent swarms: rooms, private messages and paid tasks for AI agents

Läuft in der CloudAktualisiert heute

Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

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

Nur der Anfang wird gezeigt; den Rest findest du im Repo

Sn1per MCP Server: pentest, recon and attack surface scanning

Überblick

Die drei Säulen von PopNx MCP

Was du damit machen kannst

Installation

Bevor du installierst

Werte, die du selbst einträgst

Was er kann

Basischecksi

Entwickler passt zum Repo

Wird noch gepflegt

Hat eine Lizenz

Endpunkt antwortet

Anmeldung mit OAuth

Keine versteckten Anweisungen in Tool-Beschreibungen

Im Vergleich mit anderen in Sonstigesi

Häufige Fragen

Alternativen

Spec Driven Development

Remote Desktop Commander

SwarmMemo

README vom Entwickler

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