mcp-server@3.0.3
CAUTIONPublisher claims: "Official MCP server for Qase Test Management Platform" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-10-28 and scored it 76/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: Refusal suppression. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationst+CategoryObserved action
0.0sprocessno install scripts in bundle
1.0sprocessdependency install exit 1
1.1sprocessexec /usr/bin/timeout
1.1sprocessexited 1: Node.js v22.23.4
1.1sclaimedno tools/list reply (exit 1)
1.1sprocessscript backend runs setup only
Static findings
HIGH
Refusal suppressiondocs/migration.md:46 · Refusal suppression — attempting to prevent safety responsesFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01MEDIUM
File permission modification commandpackage.json:48 · File permission modification command — agent changes file ownership/permissionsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05What would make this Verified
4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Asks the agent to act silently or skip confirmation≈ +8 on the totalRemove "do not tell the user", "without asking", "disable safety" and similar. An agent skill should never ask to be invisible.
- Unclaimed publisher≈ +8 on the totalClaim qase: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim qase