sweesama · MCP server
Read public WeChat article URLs via hosted MCP, with Markdown content and shared-cache reading.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Receipt history: every signed receipt for every version of this listing, and what changed between them.
Read public WeChat article URLs via hosted MCP, with Markdown content and shared-cache reading.
Static scanned
It runs on the maker's servers, so there is nothing to install. Point your client at this endpoint, as its own server.json declares it at commit 3a0aa8c9f655.
https://api.readgzh.site/mcp-serverAsks for Authorization (a secret), sent as a header.
What was read is the repository at that commit. Nothing on this page establishes that the endpoint runs that code: a hosted server can be redeployed from anything. Any account, plan or price it needs is the maker's to set.
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/sweesama-readgzh)Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.
Named by its own server.json. At the commit read, the repository's server.json names this server, which is the publisher's statement that this is its source. Nothing signed links the endpoint to that commit, so what answers at the endpoint may be built from something else.
MCP server for loading and extracting text from PDF files with chunked pagination and interactive viewer
Maintenance
MaintainedLast commit on the default branch 30 Sep 2026, 0 days before this check on 30 Sep 2026.
Read from the repository's default branch, read at the commit this listing pins.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
Try the connection first
The same test the directory runs: the MCP handshake, then a request for the tool list, with no credentials and never a tool call, published as scenario set mcp-connection v1.0. It says whether the endpoint answers and what it lists, not what any tool does.
It cannot be tested without credentials: its endpoint asks for Authorization, which only its users have, and this site never sends a credential.