Security flags foundOur static scan found signals worth reviewing before you trust this with an agent. See exactly what, per check, below.
Telemetry disclosureUndisclosed egress detected.Static checks found network calls the docs do not mention. Disclosed telemetry is common and fine, silent telemetry is the finding.
Security tierTier 1, Contained.No network access and no credentials. Runs entirely on its own. What tiers mean Install-time hooks & dependencies1 finding
INFOrequirements.txt — High dependency count (41). A breadth hint, not a defect by itself.
Runs code / shell commandsno flags
Whether the server can execute commands on your machine.
Secrets & credentials3 findings
HIGHsrc/mcp_server.py:872 — A secret read into 'password' at line 869 reaches a log/print sink at line 872 within the same function: a credential may leak/exfiltrate. Confirm the data path.
HIGHsrc/mcp_server.py:876 — A secret read into 'password' at line 869 reaches a log/print sink at line 876 within the same function: a credential may leak/exfiltrate. Confirm the data path.
INFOsrc/mcp_server.py:869 — Reads a secret-shaped environment variable. Ordinary for a credentialed server; recorded for completeness.
Network calls out1 finding
MEDIUMsrc/mcp_server.py:201 — Hardcoded external endpoint 'www.instagram.com'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.
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.