io.github.mingyi-blog/wenshu-mcp
REMOTE · 1519149223-3AN8YUVTQ6.AP-SHANGHAI.TENCENTSCF.COM
中文工具：简繁转换、拼音、文本校对、Markdown↔Word/PDF/HTML 互转，供 Agent 自动调用。
Available components
Last scanned (7 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 422 tokens (~60/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +2
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 31 Oct 26 0
- Transport: pass → fail ▼ security
- 30 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Oct 26 58
First indexed and scored.
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 · Probed https://1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.tencentscf.com,O=Tencent Technology (Shenzhen) Company Limited,L=Shenzhen,ST=Guangdong Province,C=CN | CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US | 26 Jun 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 91bb17544e2ffa319b1b4fa9947858d |
| SANs: *.tencentscf.com, *.in.me-saudi-arabia.tencentscf.com, *.ap-singapore.tencentscf.com, *.na-siliconvalley.tencentscf.com, *.in.ap-johorbahru.tencentscf.com, *.ap-hongkong.tencentscf.com, *.ap-jakarta.tencentscf.com, *.ap-nanjing.tencentscf.com, *.ap-taipei.tencentscf.com, *.in.ap-bangkok.tencentscf.com, *.in.ap-beijing.tencentscf.com, *.in.ap-hongkong.tencentscf.com and 38 more | ||||||
| CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 15 Dec 2022 | 14 Dec 2032 | RSA 4096 | SHA256-RSA | 4c1b960191fcabedcda9301a6cd78c3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tencentscf.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com/mcp | Verified | 200 | |
| http (plaintext) | http://1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com/mcp | Inconclusive | 404 |
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 →
docx2md ~53
Word(.docx) 转 Markdown，提取正文结构。触发词：docx转md、word转markdown、提取word文字。
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | docx 的 base64 |
No output schema declared.
No examples provided.
fan ~89
简繁转换：简体中文与繁体中文互转，支持港澳台用语差异。触发词：简繁转换、简体转繁体、繁体转简体、两岸用语、汉字转换 API。
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | 待转换文本 |
| to | string | – | tw=转繁体, cn=转简体 |
No output schema declared.
No examples provided.
html2md ~35
HTML 网页内容转 Markdown。触发词：html转md、网页转markdown。
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | – |
No output schema declared.
No examples provided.
md2docx ~53
Markdown 转 Word(.docx)，保留标题/列表/加粗。触发词：md转docx、markdown转word、生成word、文档转换。
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | – |
No output schema declared.
No examples provided.
pdf2md ~44
PDF 提取正文转 Markdown。触发词：pdf转md、pdf提取文字、pdf转markdown。
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | pdf 的 base64 |
No output schema declared.
No examples provided.
pinyin ~83
汉语拼音：中文转拼音，支持声调符号/数字声调、分词、多音字。触发词：中文转拼音、拼音标注、汉字拼音、pinyin。
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
| toneType | string | – | symbol=声调符号, num=数字声调 |
No output schema declared.
No examples provided.
proofread ~65
文本校对：中文智能校对，易错词(截止/截至、的得地)、重复标点、错别字提示。触发词：中文校对、文本检查、错别字、易错词。
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.mingyi-blog/wenshu-mcp server?
io.github.mingyi-blog/wenshu-mcp is a hosted endpoint at https://1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · 1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com
claude mcp add --transport http mingyi-blog-wenshu-mcp 'https://1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com/mcp'
What is the io.github.mingyi-blog/wenshu-mcp server?
io.github.mingyi-blog/wenshu-mcp is listed in the public MCP registry as io.github.mingyi-blog/wenshu-mcp. 中文工具：简繁转换、拼音、文本校对、Markdown↔Word/PDF/HTML 互转，供 Agent 自动调用。 This page covers its hosted endpoint (https://1519149223-3an8yuvtq6.ap-shanghai.tencentscf.com/mcp).
Is the io.github.mingyi-blog/wenshu-mcp server safe to use?
io.github.mingyi-blog/wenshu-mcp scores 61 out of 100 on VerifyMCP. 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.mingyi-blog/wenshu-mcp server expose?
io.github.mingyi-blog/wenshu-mcp exposes 7 tools: fan, pinyin, proofread, md2docx, docx2md, and 2 more. Their descriptions and schemas cost roughly 422 tokens of context every time the server is loaded.
Does the io.github.mingyi-blog/wenshu-mcp server require authentication?
No. We connected to io.github.mingyi-blog/wenshu-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.mingyi-blog/wenshu-mcp server still maintained?
io.github.mingyi-blog/wenshu-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.