zexl-mcp@0.1.0
VERIFIED· not startedPublisher claims: "MCP server for Zexl: ask your AI assistant about AI spend and waste, and connect a project in one go." 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
- no credential variables read in the code
- Where it talks to
- tryzexl.xyz (its own)Also fly.dev — not the publisher's domain; check what for before connecting.
- 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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable and talks to tryzexl.xyz, its own; the guard pins the network to what the honeypot saw and logs every call.
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-21 and scored it 84/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
"""Puts the send key into a project's .env file without the key passing through the model.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."could not check": "Could not check .gitignore; make sure .env is not committed.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.cell (notebooks). If the key is loaded from .env in code, put the import after `load_dotenv()`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Do not: put the key in source files, log it, or commit `.env`. Do not wrap or replace theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.check = subprocess.run( # noqa: S603Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- If the app already loads `.env` (python-dotenv, pydantic-settings, Django-environ, theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""A Zexl key already in the shell or in the .env file."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.The key is in the project's .env as ZEXL_API_KEY: the header takes the part before the dot. AskFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Makes sure git will not commit the .env file."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.project's .env file and save a read key for these tools. The key is never returned toFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Then call zexl_connect_finish with the path of the project's .env file. Do not ask "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.async def zexl_connect_finish(env_file: str = ".env", wait_seconds: int = 90) -> CallToolResult:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.2. Load the key from the environment. `ZEXL_API_KEY` is already in the project's `.env` fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.top = subprocess.run( # noqa: S603Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.zexl_connect_finish (it writes ZEXL_API_KEY to .env itself; never ask the user to paste a key intoFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 zexl-mcp@0.1.0 as of 26 min ago. This is the package itself, not its dependencies.