wechat-mp-mcp-server (xihe-lab/wechat-mp-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 54 out of 100, grade D. It declares 25 tools. No publisher has claimed this listing.

D
Caution
54/100

wechat-mp-mcp-server

WeChat Official Account (MP) MCP Server for AI Applications

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

xihe-lab

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: WECHAT_APP_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: WECHAT_APP_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes25 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

wechat_auth_configure

配置微信公众号 AppID 和 AppSecret

wechat_auth_get_token

获取当前 Access Token(自动刷新)

wechat_auth_refresh

强制刷新 Access Token

wechat_auth_health_check

凭据健康检查:清除本地缓存 token,强制向微信平台换取新 token 以验证凭据真实有效(可识别「缓存 token 假阳性」——本地 token 未过期但 AppSecret 已失效的情况)。失败时返回错误码、出口 IP 与操作指引

wechat_auth_sync_from_env

从环境变量同步 AppID/AppSecret 到本地存储并清除 token 缓存(解决「平台重置 secret 后本地 SQLite 仍存旧值」的问题)。优先读进程环境变量,缺失时自动解析 ~/.zshenv(或指定文件)中的 export 语句。secret 不会出现在返回结果中

wechat_draft_add

创建草稿(支持多图文,最多8篇)。注意:官方接口限制正文 <2 万字符,长文请改用 wechat_web_write_draft

wechat_draft_list

获取草稿列表

wechat_draft_get

获取草稿详情

wechat_draft_delete

删除草稿

wechat_draft_update

更新草稿中的单篇文章(官方 /draft/update 接口)。只传需要修改的字段,正文同样受 2 万字符限制

wechat_html_check

公众号正文 HTML 发布前静态检查(纯本地无网络):ul/li 残留、裸 br 换行丢失风险、占位符残留、非 mmbiz 图片、script 标签、SVG 动画双事件、去标签字数上限预警

wechat_media_upload

上传临时素材(图片/语音/视频)

wechat_media_get

获取临时素材

wechat_material_upload_image

上传永久图片素材(用于草稿封面图,返回的 media_id 可作为 thumb_media_id)

wechat_media_uploadimg

上传图文消息内的图片(正文配图专用端点),返回可直接嵌入正文 HTML 的 mmbiz URL。注意:官方 draft/add 接口会过滤非 mmbiz 域名的外链图片,正文图片必须走本接口或 wechat_web_upload_image

wechat_publish_submit

提交发布(草稿 → 发布)

wechat_publish_list

获取已发布文章列表

wechat_publish_get

获取发布状态

wechat_publish_delete

删除已发布文章

wechat_stats_article_summary

图文数据统计(web 后台 misc 接口,cookie 鉴权无 IP 白名单依赖):按日返回指定日期区间内文章的阅读/分享/点赞等数据。跨度 ≤7 天,查询昨天及更早的数据最准

wechat_stats_user_summary

用户数据统计(web 后台 misc 接口,cookie 鉴权无 IP 白名单依赖):按日返回指定日期区间内的新增关注/取关/净增等数据。跨度 ≤7 天

wechat_web_login

扫码登录公众号后台(打开 Chrome 窗口展示二维码)。登录一次后 cookie 持久保存于本地浏览器 profile,日常操作无需重复登录

wechat_web_status

检查公众号后台登录态(不报错:未登录时返回 logged_in: false 与登录指引)

wechat_web_upload_image

通过 web 编辑器通道上传图片(filetransfer 接口),返回 mmbiz 图床 URL。不依赖 IP 白名单,适合无白名单/出口 IP 多变的环境

wechat_web_write_draft

长文直写公众号草稿(编辑器通道):读取本地 HTML 文件 → lint 预检 → 外链降级 → 图片自动上图床 → operate_appmsg 创建完整草稿。不受官方接口 2 万 HTML 字符限制(限制的是去标签正文字数 ≤2 万)。返回 appMsgId 与编辑器 URL,最终发表由人工确认(每天仅 1 次群发额度)

// known CVEs in dependencies2 critical16 high9 medium21 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@1.2.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@1.2.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

highaxios@1.6.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.6.0GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.6.0GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configDATA_DIR数据存储目录,默认 ./data(浏览器登录 profile 存于其下 browser-profile/)
configWECHAT_APP_ID公众号 AppID
🔐 secretWECHAT_APP_SECRET安全提示: 是调用凭证。使用项目级配置时,请将 .workbuddy/ 加入 .gitignore,避免提交到仓库。
configWECHAT_BROWSER_CHANNELWeb 会话层使用的浏览器,默认 chrome(本机已装的 Google Chrome)
configWECHAT_BROWSER_HEADLESSWeb 会话层是否无头运行,默认 false(登录时需要可见窗口扫码)
// quality suggestions

Dependencies

6 runtime dependencies (9 dev), 1 flagged: playwright-core

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

25/25 tools missing one or more hints — wechat_auth_configure (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wechat_auth_get_token (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wechat_auth_refresh (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +22 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 1/25 tools referenced in tests (4%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 14 high severity in production deps — axios@1.6.0 (high), axios@1.6.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

4 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/xihe-lab/wechat-mp-mcp-server?variant=verified)](https://m8ven.ai/mcp/xihe-lab/wechat-mp-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 6500b55572431ad5b30941ad92debde5d8e325b5
code hash: a32ec995522c3b2459216310840f5155f636ce36c65ba7bde45a63bfc5e5a4e2
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client