原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Sn1per MCP Server: pentest, recon and attack surface scanning

作者: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 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: 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

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 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月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 1N3 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“网络安全”中的其他服务器比较i

  • 星标数多于此分类中其他 996 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 996 个服务器的 66% 更新
  • 基础检查结果等于或优于此分类中其他 996 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Sn1per MCP Server: pentest, recon and attack surface scanning 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.9.0)于21天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它?

同一分类中有:Action1 MCP by usefulapi, ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

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

在云端运行今天更新
安装

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

在云端运行今天更新
安装

作者的 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.

  1. 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

  1. 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>
  1. 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
  1. 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
  1. Register the server with Claude Code (other clients: docs/clients.md):
   claude mcp add sn1per -s user -- /home/<user>/.local/bin/sn1per-mcp --env-file /home/<user>/.config/sn1per-mcp/env
  1. 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.

ClientStatusDelete and export tools (need MCP elicitation)
Claude Code (2.1.284)verifiedyes, 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 onlyno in codex exec, which declines the confirmation; the interactive Codex interface is not yet tested
Web, mobile and remote-connector clientsnot 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.

EditionEngine dialectStatus
Sn1per Community Edition 9.2 (repository master at a5450bc)9.xverified 2026-10-12, with the server running as root
Later Sn1per Community Edition 9.x releases9.xexpected
Sn1per SE 11.0 and 11.111.xverified 2026-10-12 (11.0 as root and as a normal user through sudo, 11.1 as root)
Sn1per Enterprise, 11.3 development build11.xverified 2026-10-12, as a normal user through sudo
Other 11.x releases, including 11.211.xexpected
Sn1per Professional 202611.xuses 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.

ToolWhat it doesRead-only or changes stateAvailability
sniper_statusReports the detected edition, the scan modes available, the configured scope and why scanning may be unavailableRead-onlyAlways
list_workspacesLists the Sn1per loot workspaces on the hostRead-onlyAlways
scan_statusReports a scan's state and a redacted log tail, or whether anything runs in a workspaceRead-onlyAlways
get_findingsReads findings with severity, title, location and hostRead-onlyAlways
get_portsReads open ports with protocol, service and versionRead-onlyAlways
get_subdomainsReads discovered subdomainsRead-onlyAlways
get_technologiesReads detected web technologiesRead-onlyAlways
grep_lootSearches loot files in one workspace (or in all of them, when the operator asks) for a string or an extended regular expressionRead-onlyAlways
sniper_scanStarts a Sn1per scan of one target, as root, and returns a job handleChanges state: sends traffic to the targetAlways registered; refuses every target until you configure a scope
cancel_scanStops a scan that this server startedChanges stateAlways
delete_workspacePermanently deletes one workspace and its scan data, as root, after the human types the workspace nameChanges state: irreversibleOnly with SNIPER_MCP_ENABLE_DESTRUCTIVE=1 and a client with MCP elicitation
export_workspaceWrites a tar.gz archive of one workspace into the server's state directory, after the human types the workspace nameChanges state: writes a fileOnly 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

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx