Case file No.346 · pypi · stdio

Sn1per MCP Server: pentest, recon and attack surface scanning

io.github.1N3/sn1per-mcp · v0.9.0

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

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 6 days ago

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

101 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v0.9.0)Oct 24, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

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

MCPWatch gives Sn1per MCP Server: pentest, recon and attack surface scanning a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Sn1per MCP Server: pentest, recon and attack surface scanning have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package sn1per-mcp. That is not proof of safety.

When was Sn1per MCP Server: pentest, recon and attack surface scanning last updated?

The latest registry version is 0.9.0, published Oct 17, 2026. The last push to 1N3/sn1per-mcp was on Oct 17, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does Sn1per MCP Server: pentest, recon and attack surface scanning use?

GitHub reports the license of 1N3/sn1per-mcp as Apache-2.0.

Related servers

same publisher / similar score