helloHub1212/dsh-windows-mcp

C2

Windows desktop automation for DeepSeek Harness: the in-box MCP client bridge mounted against CursorTouch/Windows-MCP, with an off-by-default Computer Use switch and an in-app dependency installer.

★ 100+ · helloHub1212/dsh-windows-mcp source on GitHub · this plugin in the registry

helloHub1212/dsh-windows-mcp is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, command execution in build output only, executes commands in development tooling the package does not ship.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
can rewrite the system promptprompt_surfacesystem-prompt/assemble
command execution in build output onlyexec_bundled×2 in build output only, e.g. lib/dependency.js:23, lib/dependency.js:195
executes commands in development tooling the package does not shipexec_tooling×8 in development tooling the package does not ship, e.g. scripts/dump-config.mjs:22, scripts/dump-config.mjs:22

Tool registrations

2 static tool registration point(s).

Services it injects

slots

Hooks it attaches

system-prompt/assemble

Outbound domains

docs.astral.sh pypi.org mirrors.ustc.edu.cn mirrors.aliyun.com mirrors.cloud.tencent.com repo.huaweicloud.com mirrors.nju.edu.cn pypi.tuna.tsinghua.edu.cn

Environment variables it reads

DSH_HOME UV_TOOL_DIR APPDATA PATHEXT

How to read this

Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.

Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.