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の3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

利用者の声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がつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

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

このカテゴリのほかの993件のうち0%よりスターが多い
このカテゴリのほかの993件のうち66%より最近レジストリに公開
基本チェックの結果が、このカテゴリのほかの993件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Sn1per MCP Server: pentest, recon and attack surface scanningは安全ですか？

当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか？

レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。

パソコンで動きますか、それともクラウドですか？

あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません（サーバー自体がオンラインサービスを呼び出す場合を除きます）。

今もメンテナンスされていますか？

GitHubリポジトリの最終更新は–、最新バージョン（0.9.0）がレジストリに届いたのは21 日前です。

どのアプリで使えますか？

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにPython (uv)も必要です。

代わりに使えるものは？

同じカテゴリには：ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi, Lambda Labs MCP by usefulapi

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

ipdata MCP by usefulapi

作者：m190

Look up location, network, company and threat data for IP addresses and ASNs in ipdata.

クラウドで動く今日更新

インストール

MaxMind minFraud MCP by usefulapi

作者：m190

MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.

クラウドで動く今日更新

インストール

Lambda Labs MCP by usefulapi

作者：m190

Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.

クラウドで動く今日更新

インストール

作者の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の3つの柱

できること

インストール

インストールの前に

自分で入力する値

できること

基本チェックi

作者とリポジトリが一致

今もメンテナンスされている

ライセンスがある

エンドポイントが応答する

OAuthでサインイン

ツールの説明に隠れた指示がない

サイバーセキュリティのほかのサーバーとの比較i

よくある質問

代わりの候補

ipdata MCP by usefulapi

MaxMind minFraud MCP by usefulapi

Lambda Labs MCP by usefulapi

作者の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