io.github.datoushiwo/wechat-writer-mcp
NPM · WECHAT-WRITER-MCP
面向技术博主的 AI 内容加工流水线 MCP —— 从原始素材到公众号草稿箱
Available components
Last scanned (19 hours ago)
Scores higher than 87% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 82 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 477 tokens (~119/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.93 functional
- 22 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/wechat-writer-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
estimate_originality ~84
对内容做原创度自评，辅助决策是否点"原创"标记。基于用户自己的历史草稿做比对，不能替代微信官方查重。
| Name | Type | Req | Description |
|---|---|---|---|
| check_against_history | boolean | – | 是否与草稿箱历史内容比对 |
| content | string | yes | 待检查的文章内容（markdown 或纯文本） |
No output schema declared.
No examples provided.
import_source ~95
导入原始内容（本地 markdown 文件或 URL 网页），准备进行公众号加工。返回 raw_markdown 和元数据。
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | 本地文件路径（source_type=file 时必填） |
| source_type | string | yes | 来源类型：file 读取本地文件，url 抓取网页正文 |
| url | string | – | 网页 URL（source_type=url 时必填） |
No output schema declared.
No examples provided.
save_to_wechat_draft ~204
将加工好的内容存入公众号草稿箱。永远只存草稿，不会自动群发/发布。存入后需手动到公众号后台发布。
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | 作者名（默认使用环境变量配置） |
| content_source_url | string | – | 原文链接（可选） |
| cover_path | string | – | 封面图片路径（cover_strategy=specified 时使用） |
| cover_strategy | string | – | 封面策略：random_from_folder 从目录随机选、specified 指定路径、none 不设封面 |
| digest | string | – | 摘要（不超过 120 字） |
| html_content | string | yes | 文章 HTML 正文（transform_for_wechat 的输出） |
| need_open_comment | boolean | – | 是否打开评论 |
| only_fans_can_comment | boolean | – | 是否仅粉丝可评论 |
| title | string | yes | 文章标题 |
No output schema declared.
No examples provided.
transform_for_wechat ~94
将 markdown 内容转换为公众号适配的 HTML 格式。自动段落切分、代码块处理、超链接转脚注、添加头尾模板，并生成 3 个标题候选。
| Name | Type | Req | Description |
|---|---|---|---|
| apply_template | boolean | – | 是否应用头尾模板 |
| raw_markdown | string | yes | 原始 markdown 内容 |
| title | string | – | 文章原标题（用于生成标题候选） |
No output schema declared.
No examples provided.
How do I install the io.github.datoushiwo/wechat-writer-mcp server?
io.github.datoushiwo/wechat-writer-mcp runs locally as an npm package, launched with npx -y wechat-writer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · wechat-writer-mcp
claude mcp add datoushiwo-wechat-writer-mcp -- npx -y wechat-writer-mcp
What is the io.github.datoushiwo/wechat-writer-mcp server?
io.github.datoushiwo/wechat-writer-mcp is listed in the public MCP registry as io.github.datoushiwo/wechat-writer-mcp. 面向技术博主的 AI 内容加工流水线 MCP, 从原始素材到公众号草稿箱. This page covers its npm package (wechat-writer-mcp).
Is the io.github.datoushiwo/wechat-writer-mcp server safe to use?
io.github.datoushiwo/wechat-writer-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.datoushiwo/wechat-writer-mcp server expose?
io.github.datoushiwo/wechat-writer-mcp exposes 4 tools: import_source, transform_for_wechat, estimate_originality, save_to_wechat_draft. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.
Is the io.github.datoushiwo/wechat-writer-mcp server still maintained?
io.github.datoushiwo/wechat-writer-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.datoushiwo/wechat-writer-mcp server under?
io.github.datoushiwo/wechat-writer-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.datoushiwo/wechat-writer-mcp server?
VerifyMCP ran 16 checks on io.github.datoushiwo/wechat-writer-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.