gezel-mcp@1.3.0
VERIFIED· not startedPublisher claims: "Gezel's Model Context Protocol server: gives gezels and other MCP clients access to memory, workspace files, artifacts, tasks, and team tools." 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
GEZEL_MCP_AUTHORIZED_TOOLSConfiguration, not credentials: GEZEL_CAMERAS_ENABLED, GEZEL_CONNECTORS_ENABLED, GEZEL_CRAFTBOOK_ID, GEZEL_CRAFTBOOK_STEP_EDITING, GEZEL_HOME, GEZEL_MAIL_ENABLED, GEZEL_MCP_ALLOW, GEZEL_MCP_EXCLUDE, GEZEL_MCP_LEGACY_TOOLS, GEZEL_MCP_NO_MAIN, GEZEL_MCP_SCHEMA_LINT, GEZEL_MCP_TOOL_NAMING, GEZEL_PERMISSION_PROMPT, GEZEL_SCRIPT_TOOLS, GEZEL_SOCIAL_ENABLED, PLAYWRIGHT_BROWSERS_PATH, SQUISQ_FFMPEG- Where it talks to
- no vendor host named in the code
- 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. It asks for GEZEL_MCP_AUTHORIZED_TOOLS 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-12 and scored it 93/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 · 8 s · 2 scenarios · 0 deviationsStatic findings
No findings across 4,231 lines in 13 files.
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 @bendyline/gezel-mcp@1.3.0 as of 2d ago. This is the package itself, not its dependencies.