dsh-mcp-btwy@1.2.4
VERIFIED· startup onlyPublisher claims: "Expose DeepSeek Harness sessions, agents, and tools to any other agent harness over the Model Context Protocol." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
DSH_MCP_TOKENConfiguration, not credentials: DSH_HOME, DSH_MCP_CLIENT, DSH_MCP_TIMEOUT_MS, DSH_MCP_URL, DSH_PROFILE, DSH_WEB_URL- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for DSH_MCP_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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 (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 20 s · 2 scenariosStatic findings
throw new Error('dsh-mcp-server: "allowedConfigOrigins" must be an array of absolute http(s) origins.')Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.`dsh-mcp-server: "allowedConfigOrigins" entries must be absolute origins like "http://host:23022" (got ${JSON.stringify(entry)}).`,Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.* @module dsh-mcp-server/http-routeFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
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
No advisories in OSV for dsh-mcp-btwy@1.2.4 as of 11 h ago. This is the package itself, not its dependencies.