wechat-mcp-publisher@0.2.1
VERIFIED· not startedPublisher claims: "微信公众号草稿发布本地 MCP 工具(官方 mcp SDK、stdio、token 内部管理)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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 qq.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-21 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 · 0 s · 2 scenarios · 0 deviationsStatic findings
"""三层优先级解析(通用,bool/str 皆可):用户入参 > .env 变量 > 内置默认。"""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. 在项目根目录创建 .env 文件(参考 .env.example):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.40013: "AppID 无效,请检查 .env 中的 WECHAT_APP_ID",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.40125: "AppSecret 无效,请检查 .env 中的 WECHAT_APP_SECRET",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 可配置默认值(优先级:入参 > .env > 此处)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.need_open_comment: 是否开启留言(可选,不传用 .env 或默认开启)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""配置管理:从环境变量或 .env 文件加载单账号凭据与行为开关。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.author: 作者名(可选,不传用 .env 或默认空;传空字符串可显式覆盖 .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""三层解析留言开关(入参 > .env > 内置默认),输出微信要求的 0/1 整数。"""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.only_fans_can_comment: 是否仅粉丝可评论(可选,不传用 .env 或默认关闭)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 wechat-mcp-publisher@0.2.1 as of 48 min ago. This is the package itself, not its dependencies.