bobleer/deepseek-harness-plugin-mcp
C3MCP server that lets any agent discover, install, and run DeepSeek Harness plugins (topic: dsh-plugin).
★ 1+ · bobleer/deepseek-harness-plugin-mcp source on GitHub · this plugin in the registry
bobleer/deepseek-harness-plugin-mcp is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, starts a network server, reads credential-class env vars.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×4 src, e.g. src/profile/dsh-cli.ts:1, src/profile/dsh-cli.ts:1 |
| starts a network server | net_server | ×1 src, e.g. src/mcp/http.ts:41 |
| reads credential-class env vars | token_env | GH_TOKEN, GITHUB_TOKEN |
Services it injects
tools
Hooks it attaches
tools/change
Outbound domains
api.github.com
Environment variables it reads
GITHUB_TOKEN GH_TOKEN DSH_PLUGIN_MCP_HOST DSH_PLUGIN_MCP_PORT DSH_ROOT DSH_PLUGIN_MCP_PROFILE DSH_PLUGIN_MCP_CACHE_DIR DSH_PLUGIN_MCP_CACHE_TTL_MS DSH_PLUGIN_MCP_CATALOG DSH_HOME
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.