No flags in static checksWe ran the static security checks and none of them tripped. This is not a clean-bill or a safety guarantee, it is the result of the specific checks listed below.
Telemetry disclosureNone detected.No undisclosed network egress turned up in static checks. That is not proof the tool sends nothing once it runs.
Security tierTier 3, Credentialed.Handles a real credential or real external access. What tiers mean Install-time hooks & dependencies1 finding
INFOpackage.json — npm 'prepare' lifecycle hook: install hook runs a build at install (recognized toolchain), standard for a compiled package. Recorded for completeness, not a flag.
Runs code / shell commandsno flags
Whether the server can execute commands on your machine.
Secrets & credentials2 findings
INFOindex.ts:19 — Reads a secret-shaped environment variable. Ordinary for a credentialed server; recorded for completeness.
INFOindex.ts:20 — Reads a secret-shaped environment variable. Ordinary for a credentialed server; recorded for completeness.
Network calls outno flags
Hardcoded endpoints it reaches beyond what it documents.
Prompt-injection passthroughno flags
Whether it pipes untrusted external content back as agent instructions.
Permission scope breadthno flags
How much access it asks for versus what its job needs.
How to read this: these are static checks over the source at a point in time. They catch the patterns above, not everything. Absence of a flag is not absence of danger, and a tool that runs cleanly can still behave differently once installed. We do not call any tool simply "safe". Runtime-behavior checks are the next layer we are adding.