ubiquiti-unifi-blade-mcp@0.9.2
VERIFIED· not startedPublisher claims: "Ubiquiti UniFi MCP Server — monitoring, security, and full Integration-API resource management (networks/VLANs, WiFi, firewall, ACL, DNS, vouchers)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
UNIFI_API_KEYUNIFI_MCP_API_TOKENUNIFI_PASSWORDUNIFI_TOTP_SECRETConfiguration, not credentials: UNIFI_CONTROLLERS, UNIFI_HOST, UNIFI_LOG_LEVEL, UNIFI_MCP_HOST, UNIFI_MCP_PORT, UNIFI_MCP_TRANSPORT, UNIFI_PORT, UNIFI_SITE, UNIFI_USERNAME, UNIFI_VERIFY_SSL, UNIFI_WRITE_ENABLED- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- 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. It asks for UNIFI_API_KEY, UNIFI_MCP_API_TOKEN, UNIFI_PASSWORD, UNIFI_TOTP_SECRET and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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-20 and scored it 88/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 deviationsStatic findings
…``` ## Live dev sandbox - Disposable UniFi OS Server / UniFi Network target: `https://10.1.70.14:11443` (`UNIFI_HOST=10.1.70.14`, `UNIFI_PORT=11443`, `UNIFI_VERIFY_SSL=false`; …Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.API Key Created — copy nowFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
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 ubiquiti-unifi-blade-mcp@0.9.2 as of 2 min ago. This is the package itself, not its dependencies.