backlog-mcp-server@0.23.4
VERIFIED· not startedPublisher claims: "[](https://mcptoplist.com/server/glama%2Fnulab%2Fbacklog-mcp-server)  ; the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-19 and scored it 87/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 · 10 s · 2 scenarios · 0 deviationsStatic findings
// .env file is optionalFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…server --- [](https://mcptoplist.com/server/glama%2Fnulab%2Fbacklog-mcp-server)   => Promise<HttpMcpServerHandle>;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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 backlog-mcp-server@0.23.4 as of 2 h ago. This is the package itself, not its dependencies.