Skills/Glama/dsh-codex-mcp

dsh-codex-mcp@0.3.0

VERIFIED

Publisher claims: "Enables Codex to delegate tasks to a visible DeepSeek Harness desktop session by opening it, sending or resuming tasks, and returning results while exposing connection and busy status." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher m3145284542-dotcom · publishing for 1 daysInstalls 0Last detonated 19 h ago
$npx skills add dsh-codex-mcp
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso microsoft.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Connect it under the guard; read the third-party hosts first. The code names microsoft.com as well as its own vendor. The guard pins the network to the hosts the honeypot saw.

$vet-skills run --net declared -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios) on 2026-11-13 and scored it 81/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 20 s · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.1sprocessexited 1: Harness desktop profile does not exist. Install Harness, open it once and complete setup, then retry.
20sclaimed4 tools: dsh_open, dsh_status, dsh_task, dsh_resume
20stoolsaa2745ab70994844
20stoolsd5306929875abfe7
20stools67a585824cdd5c9a
20stools727c32cbef6c39f7
20sprocessscript backend runs setup only
20sprocesssecond launch, clock +45 days, CI unset
20sprocessexited 1: Harness desktop profile does not exist. Install Harness, open it once and complete setup, then retry.

Static findings

LOW
Unpinned dependencyserver.mjs:73 · Unpinned dependency'dsh CLI not found. Install it with `npm i -g @deepseek-ai/dsh@next` ' +Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06
HIGH
Collapsed <details> block carrying instructionsREADME.md:55 · Collapsed <details> block carrying instructions<summary>安装位置与选项</summary> 默认会安装到: ```text ~/.codex/mcp/dsh-codex-mcp/ MCP 与桌面插件 ~/.codex/skills/deepseek-delegation/ Codex 技能 ~/.codex/config.toml dsh MCP 条目 ~Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathsscripts/install.mjs:18 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslet envIndex = sections.findIndex(section => /^\[mcp_servers\.dsh\.env\]\s*(?:\r?\n|$)/.test(section));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
≈2,943 tok
2 files · 20 in bundle
Tool list per prompt
≈565 tok
4 tools · 141 per tool
Handshake
184 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 216

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

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.