Skills/npm/unifi-mcp

unifi-mcp@0.2.16

VERIFIED· startup only

Publisher claims: "Model Context Protocol server for the UniFi Local Network Integration API." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher robinbowes · publishing for 132 daysInstalls 1,888Last detonated 13 h ago
$claude mcp add unifi-mcp -- npx -y @robinbowes/unifi-mcp
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials
Needs
UNIFI_API_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

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
no credential variables read in the code; at startup it asked for UNIFI_API_KEY
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @robinbowes/unifi-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; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 93/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 (it asks for UNIFI_API_KEY); 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 · 55 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
15sprocessdependency install exit 0
35sprocessrelaunched with a decoy UNIFI_API_KEY (tagged; nothing real)
55sclaimedstartup only: exited before answering, asking for UNIFI_API_KEY (a decoy value was refused)
55sprocessscript backend runs setup only
55sprocessno install scripts to re-run

Static findings

No findings across 1,197 lines in 38 files.

Cost to the agent

Instructions loaded
≈56 tok
1 file · 38 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 @robinbowes/unifi-mcp@0.2.16 as of 13 h ago. This is the package itself, not its dependencies.

unifi-mcp@0.2.16 safety verdict: Verified (startup only) — KillerSkills