gryzzly-mcp@r1
VERIFIED· install onlyPublisher claims: "Gryzzly time tracking: log time in plain language (project names, "2h30", "yesterday"), weekly timesheets with missing-day detection, and all 50 Gryzzly v1 API endpoints." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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
- gryzzly.io (its own)Also example.test — 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
- use of the skill by an agent
Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable and talks to gryzzly.io, 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 gryzzly-mcp@r1 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-18 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 · 1 scenarios · 0 deviationsStatic findings
.env("GRYZZLY_LOG", "warn")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary><b>With Docker</b></summary> ```bash docker build -t mcp-gryzzly . docker run --rm -i -e GRYZZLY_API_KEY=… mcp-gryzzly ``` The image runs unprivileged Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct..env("GRYZZLY_BASE_URL", fake.base_url())Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose..env("PATH", std::env::var("PATH").unwrap_or_default())Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose..env("PATH", std::env::var("PATH").unwrap_or_default())Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary><b>Any client, over HTTP</b></summary> Point it at `http://127.0.0.1:8080/mcp` after starting the server with `--http 127.0.0.1:8080`. See [below](#runFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct..env("PATH", std::env::var("PATH").unwrap_or_default())Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose..env("GRYZZLY_LOG", "warn")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose..env("GRYZZLY_API_KEY", "test-key")Fix: 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. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.