mseep-zen-mcp-server@5.11.1
CAUTION· not startedPublisher claims: "AI-powered MCP server with multiple model providers" 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: Caution 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
CUSTOM_API_KEYDIAL_API_KEYGEMINI_API_KEYMAX_MCP_OUTPUT_TOKENSOPENAI_API_KEYOPENROUTER_API_KEYXAI_API_KEYConfiguration, not credentials: CUSTOM_API_URL, CUSTOM_MODEL_NAME, DEFAULT_MODEL, DEFAULT_THINKING_MODE_THINKDEEP, DIAL_API_HOST, DIAL_API_VERSION, DISABLED_TOOLS, LOCALE, VENV_PATH- Where it talks to
- no vendor host named in the codeAlso dialx.ai, x.ai, pyenv.run, pypa.io, githubusercontent.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 dialx.ai, x.ai, pyenv.run, pypa.io, githubusercontent.com as well as its own vendor. The guard injects CUSTOM_API_KEY, DIAL_API_KEY, GEMINI_API_KEY, MAX_MCP_OUTPUT_TOKENS, OPENAI_API_KEY, OPENROUTER_API_KEY, XAI_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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-12 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Direct script execution from GitHub raw URL. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.print_error ".env.example not found!"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Proper API keys configured in `.env` fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.github_url = "https://raw.githubusercontent.com/BeehiveInnovations/zen-mcp-server/main/config.py"Fix: Pin versions and sources; vendor anything fetched at install time.echo "sudo apt update && sudo apt install -y python3-venv python3-pip"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# Try to load environment variables from .env file if dotenv is availableFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Create/update .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file = script_dir / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env", # EnvironmentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# This ensures .env is loaded regardless of the current working directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if [[ -f .env ]]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.print_success ".env file already exists"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo " curl https://pyenv.run | bash" >&2Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.echo "sudo apt update && (sudo apt install -y python${version_suffix}-venv python${version_suffix}-dev || sudo apt install -y python3-venv python3-pip)"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# Load environment variables from .env file in the script's directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if [[ ! -f .env.example ]]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Setup .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.content, tokens = read_file_content("/etc/passwd")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN mkdir -p tmp && chown -R zenuser:zenuser tmpFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.&& rm -rf /var/lib/apt/lists/* \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# - prompt.txt file content (alternative user input method)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.assert "--- END FILE: /etc/passwd ---" in contentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN mkdir -p logs && chown -R zenuser:zenuser logsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.RUN chmod +x /usr/local/bin/healthcheck.pyFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod +x "$zen_wrapper"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.assert "--- BEGIN FILE: /etc/passwd ---" in contentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# In the new security model, safe files like /etc/passwdFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo " curl https://pyenv.run | bash" >&2Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 mseep-zen-mcp-server@5.11.1 as of 41 h ago. This is the package itself, not its dependencies.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Pipe-to-shell pattern≈ +9 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Unclaimed publisher≈ +8 on the totalClaim mseep-support: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Direct script execution from GitHub raw URL≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Destructive file system command detected≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.