Skills/PyPI/netlicensing-mcp

netlicensing-mcp@0.1.11

VERIFIED· not started

Publisher claims: "MCP server for the Labs64 NetLicensing license management API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher labs64 · publishing for 241 daysInstalls 566Last detonated 36 h ago
$claude mcp add netlicensing-mcp -- uvx netlicensing-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
NETLICENSING_API_KEYConfiguration, not credentials: MCP_CONSOLE_BASE_URL, MCP_HOST, MCP_PORT, MCP_REDACT_FIELDS, MCP_TRANSPORT, MCP_VERBOSE, NETLICENSING_ALLOW_DEMO, NETLICENSING_BASE_URL
Where it talks to
netlicensing.io (its own)Also amazon.com — 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 amazon.com as well as its own vendor. The guard injects NETLICENSING_API_KEY only into requests to netlicensing.io (and its subdomains) and refuses the rest.

$vet-skills run --secrets NETLICENSING_API_KEY=netlicensing.io -- uvx netlicensing-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 85/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
Privileged sudo command.github/workflows/netlicensing-release.yml:154 · Privileged sudo command — agent may execute with elevated privilegessudo mv mcp-publisher /usr/local/bin/Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Destructive file system command detected.github/workflows/netlicensing-release.yml:213 · Destructive file system command detecteddocker run -i --rm \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Destructive file system command detectedAGENTS.md:26 · Destructive file system command detected# Lint / format / type-check (these are the exact CI checks)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
File permission modification command.github/workflows/netlicensing-release.yml:153 · File permission modification command — agent changes file ownership/permissionschmod +x mcp-publisherFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈2,206 tok
3 files · 74 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 netlicensing-mcp@0.1.11 as of 34 h ago. This is the package itself, not its dependencies.

netlicensing-mcp@0.1.11 safety verdict: Verified (not started) — KillerSkills