Remote MCP · Endpoint

ReadGZH MCP server

No. ReadGZH answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.readgzh.site/mcp-server

The last check completed an MCP handshake.

Registry name
io.github.sweesama/readgzh
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
648 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read WeChat public account articles via MCP. 99.89% anti-scraping success, 50-87% token compression.
Repository
https://github.com/sweesama/readgzh
Listing
From the official MCP registry (active).
Recent checks of ReadGZH
CheckedResultHandshake
1 hour agoHandshake completed648 ms
2 days agoHandshake completed677 ms
4 days agoHandshake completed1.00 s
5 days agoHandshake completed606 ms
7 days agoHandshake completed857 ms
8 days agoHandshake completed718 ms
9 days agoHandshake completed587 ms
12 days agoHandshake completed641 ms
13 days agoHandshake completed617 ms
15 days agoHandshake completed758 ms
17 days agoHandshake completed677 ms
18 days agoHandshake completed1.22 s
19 days agoHandshake completed799 ms
20 days agoHandshake completed959 ms
20 days agoHandshake completed643 ms
21 days agoHandshake completed1.21 s
22 days agoHandshake completed701 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with ReadGZH and makes no claim about it beyond what these checks measured.