Skills/PyPI/offsec-mcp

offsec-mcp@0.1.0

VERIFIED· not started

Publisher claims: "MCP server that gives AI agents authorized-only offensive-security tools: recon, CVE intel, JS analysis, port scanning." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher nadirzhon · publishing for 98 daysInstalls 74Last detonated 22 h ago
$claude mcp add offsec-mcp -- uvx offsec-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
NVD_API_KEYConfiguration, not credentials: OFFSEC_ALLOW_ANY, OFFSEC_SCOPE, OFFSEC_SCOPE_FILE
Where it talks to
no vendor host named in the codeAlso crt.sh, cloudflare-dns.com, rdap.org, nist.gov — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names crt.sh, cloudflare-dns.com, rdap.org, nist.gov as well as its own vendor. The guard injects NVD_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx offsec-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
GitHub token pattern detectedtests/test_tools.py:20 · GitHub token pattern detected — possible hardcoded or harvested tokenconst gh = "ghp_0123456789012345678901234567890123456";Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
AWS access key pattern detectedtests/test_tools.py:18 · AWS access key pattern detected — possible hardcoded or harvested keyconst AWS = "AKIAIOSFODNN7EXAMPLE";Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03

Cost to the agent

Instructions loaded
≈65 tok
1 file · 19 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for offsec-mcp@0.1.0 as of 22 h ago. This is the package itself, not its dependencies.