Is dsh-zhihu@0.2.0 safe to install?

dsh-zhihu@0.2.0

VERIFIED· startup only

Publisher claims: "Enables MCP clients to use their own Zhihu account to view recommendations, read answer and article content, track specified users' creations and public likes, and optionally vote up after fully reading. Access is session-bound and uses separate pause states for direct HTTP and browser channels." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher gstarmin · publishing for 0 daysInstalls 0Last detonated 8 h ago

$npx skills add dsh-zhihu

Watch Report 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

It will ask for: no credential variables read in the code
Where it talks to: no vendor host named in the codeAlso zhihu.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: the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$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 (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 86/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 · 25 s · 2 scenarios · 0 deviations

t+CategoryObserved action

0.0sprocessno install scripts in bundle

5.3sprocessdependency install exit 0

25sclaimedstartup only: exited (0) before answering · (node:1976) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) dsh-zhihu init | serve | admin-token Environment: DSH_ZHIHU_HOME, DSH_ZHIHU_PORT, DSH_ZHIHU_CHROMIUM

25sprocessscript backend runs setup only

25sprocessno install scripts to re-run

Static findings

MEDIUM

URL with embedded credentialstests/http.test.mjs:11 · URL with embedded credentials — may be phishing or credential leaking

for(const url of ['https://evil.test/','http://www.zhihu.com/','https://www.zhihu.com:444/','https://[email protected]/'])await assert.rejects(context.get(url),/不允许/);