Skills/npm/dsh-mcp-manager

dsh-mcp-manager@0.2.2-rc.2

CAUTION· install only

Publisher claims: "MCP server manager: a settings-driven fleet of mcp-client instances with runtime status, restart, and probe" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher deepseek-ai · publishing for 8 daysInstalls 63,554Last detonated 16 h ago

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
5 of 5 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 78/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: Access to sensitive file paths; Collapsed <details> block carrying instructions; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessexited 1: Node.js v22.23.5
0.2sprocessbundled script run in the sandbox with no arguments
0.3sprocessexited 1: Node.js v22.23.5
0.3sprocessbundled script run in the sandbox with no arguments
0.4sprocess5 of 5 bundled scripts run with no arguments
0.4sprocessscript backend runs setup only
0.4sprocessscript backend runs setup only
0.4sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathslib/index.js:85 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files...Object.entries(entry.env).map(([key, value]) => [value, `${path}.env.${key}`]),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Collapsed <details> block carrying instructionsREADME.md:187 · Collapsed <details> block carrying instructions<summary>Working context for maintainers — click to expand</summary> This Dev Note is working context for maintainers: open design questions and directions thatFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathssrc/index.ts:110 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files...Object.entries(entry.env).map(([key, value]): [string, string] => [value, `${path}.env.${key}`]),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathslib/types/index.js:82 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files...Object.entries(entry.env).map(([key, value]) => [value, `${path}.env.${key}`]),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈60 tok
1 file · 25 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for @deepseek-ai/dsh-mcp-manager@0.2.2-rc.2 as of 16 h ago. This is the package itself, not its dependencies.

What would make this Verified

2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim deepseek-ai: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. 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.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim deepseek-aiPropose a patch to the maintainer