ReadGZH
REMOTE · API.READGZH.SITE · SCANNED OCT 4
Read WeChat public account articles via MCP. 99.89% anti-scraping success, 50-87% token compression.
Available components
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 Security51
- 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 connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 400, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the ReadGZH MCP server?
ReadGZH is a hosted endpoint at https://api.readgzh.site/mcp-server, 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 · api.readgzh.site
claude mcp add --transport http sweesama-readgzh 'https://api.readgzh.site/mcp-server'
{
"mcpServers": {
"sweesama-readgzh": {
"url": "https://api.readgzh.site/mcp-server"
}
}
} {
"servers": {
"sweesama-readgzh": {
"type": "http",
"url": "https://api.readgzh.site/mcp-server"
}
}
} [mcp_servers.sweesama-readgzh] url = "https://api.readgzh.site/mcp-server"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sweesama-readgzh": {
"type": "remote",
"url": "https://api.readgzh.site/mcp-server",
"enabled": true
}
}
} openclaw mcp add sweesama-readgzh --url 'https://api.readgzh.site/mcp-server' --transport streamable-http
mcp_servers:
sweesama-readgzh:
url: "https://api.readgzh.site/mcp-server" {
"McpServers": {
"sweesama-readgzh": {
"Transport": "http",
"Url": "https://api.readgzh.site/mcp-server"
}
}
} assistant mcp add sweesama-readgzh -t streamable-http -u 'https://api.readgzh.site/mcp-server'
{
"mcpServers": {
"sweesama-readgzh": {
"type": "http",
"url": "https://api.readgzh.site/mcp-server"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 −42
- Tool safety: pass → unverified ▼ security
- Stability: 0.90 → 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
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 3 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 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
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.90 ▲ functional
- 2 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 1 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 29 Sept 26 −40
- Tool safety: pass → unverified ▼ security
- Stability: 0.73 → 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
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 26 +40
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −39
- Tool safety: pass → unverified ▼ security
- Stability: 0.67 → 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
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 7 Oct 2026 · Probed https://api.readgzh.site/mcp-server
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=readgzh.site | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 291c9b3c7ae9933b13539b9b582573ca |
| SANs: readgzh.site, api.readgzh.site | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.readgzh.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| readgzh.site. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.readgzh.site/mcp-server | Verified | 200 | |
| http (plaintext) | http://api.readgzh.site/mcp-server | Inconclusive | 400 |
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 →
No tool schema has been captured from this endpoint yet.
What is the ReadGZH MCP server?
ReadGZH is an MCP server listed in the public MCP registry as io.github.sweesama/readgzh. Read WeChat public account articles via MCP. 99.89% anti-scraping success, 50-87% token compression. This page covers its hosted endpoint (https://api.readgzh.site/mcp-server).
Is the ReadGZH MCP server safe to use?
ReadGZH scores 32 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.
Does the ReadGZH MCP server require authentication?
No. We connected to ReadGZH without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ReadGZH MCP server still maintained?
ReadGZH is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.