Skills/npm/dsh-mcp-btwy

dsh-mcp-btwy@1.0.4

VERIFIED· startup only

Publisher 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.

Registry npm (MCP server)Publisher baitouwuya · publishing for 18 daysInstalls 3,173Last detonated 7d ago
$claude mcp add dsh-mcp-btwy -- npx -y dsh-mcp-btwy
WatchReport an issue

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

Code inventory arrives with this version's next honeypot run.
It will ask for
unknown until the next run
Where it talks to
unknown until the next run
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

Not enough was observed to say yet. Startup only; authenticated tool behavior not tested. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try dsh-mcp-btwy` runs it now and prints the full answer.

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-08 and scored it 81/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 · 0 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sfilesystemread ~/.dsh/mcp/dsh-mcp-endpoint.json outside project
0.1sprocessexec /usr/bin/date
0.1sprocessexec /usr/bin/timeout
0.1sprocessexec /app/apps/web/node_modules/.bin/ps
0.1sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/ps
0.1sprocessexec /app/node_modules/.bin/ps
0.1sprocessexec /pnpm/ps
0.1sprocessexec /usr/local/sbin/ps
0.1sprocessexec /usr/local/bin/ps
0.1sprocessexec /usr/sbin/ps
0.1sprocessexec /usr/bin/ps
0.1sprocessexec /sbin/ps
0.1sprocessexec /bin/ps
0.1sclaimedno tools/list reply (exit 0)
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
MCP server using network transport (SSE/HTTP)lib/http-route.js:27 · MCP server using network transport (SSE/HTTP) — data sent over network* @module dsh-mcp-server/http-routeFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

No other findings across 11,850 lines in 48 files.

Cost to the agent

Instructions loaded
≈64 tok
1 file · 48 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
64 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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.0.4 as of 7d ago. This is the package itself, not its dependencies.