Sn1per MCP Server: pentest, recon and attack surface scanning

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

제작자: 1N3버전 0.9.0i★ –i내 컴퓨터에서 실행

레지스트리 이름io.github.1N3/sn1per-mcp

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: stdio
카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
직접 입력할 값: 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

필요한 것

PyPIPython의 uv 설치(uvx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 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"
      }
    }
  }
}

터미널에서 이 명령어를 실행하세요

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

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.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"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

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.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 1N3 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 32725개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 32725개 중 65%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 32725개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Sn1per MCP Server: pentest, recon and attack surface scanning, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.9.0)은 20일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Signoff

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

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

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트

설치

Remote Desktop Commander

제작자: desktop-commander

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

클라우드에서 실행★ 211그저께 업데이트

설치

Signoff

제작자: ayuanxx-max

Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.

내 컴퓨터에서 실행오늘 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

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

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

Sn1per MCP Server: pentest, recon and attack surface scanning

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

직접 입력할 값

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

Signoff

제작자의 README

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