Remote MCP · Endpoint

人生增值(zengzhi.life)MCP MCP server

No. 人生增值(zengzhi.life)MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://zengzhi.life/mcp

The last check completed an MCP handshake.

Registry name
life.zengzhi/zengzhi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
697 ms
Tools exposed
10 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
人生增值 ZengZhi — 个人数字资产审计/撮合平台 (digital-asset audit/matchmaking): 公开 tools 免 Key, 个人数据需 Bearer zzk_.
Listing
From the official MCP registry (active).
Recent checks of 人生增值(zengzhi.life)MCP
CheckedResultHandshake
1 hour agoHandshake completed697 ms
2 days agoHandshake completed813 ms
5 days agoHandshake completed751 ms
7 days agoHandshake completed720 ms
9 days agoFailed - the request timed out—
11 days agoHandshake completed727 ms
13 days agoHandshake completed847 ms
15 days agoHandshake completed996 ms
17 days agoHandshake completed716 ms
18 days agoHandshake completed738 ms
20 days agoHandshake completed1.84 s
21 days agoHandshake completed805 ms
23 days agoHandshake completed775 ms
25 days agoFailed - the hostname does not resolve—

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with 人生增值(zengzhi.life)MCP and makes no claim about it beyond what these checks measured.