Remote MCP · Endpoint

JiZhiMCP MCP server

No. JiZhiMCP answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.xn--5kvtwv52d.com/mcp

The last check completed an MCP handshake.

Registry name
com.xn--5kvtwv52d/jizhineng-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.62 s
Tools exposed
22 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Host any HTTP API as MCP tools with a tamper-evident cross-agent settlement ledger.
Listing
From the official MCP registry (active).
Recent checks of JiZhiMCP
CheckedResultHandshake
34 minutes agoHandshake completed3.62 s
3 days agoHandshake completed849 ms
13 days agoHandshake completed658 ms
13 days agoHandshake completed727 ms
15 days agoHandshake completed835 ms
16 days agoHandshake completed745 ms
17 days agoHandshake completed768 ms
18 days agoHandshake completed751 ms
18 days agoHandshake completed768 ms
20 days agoHandshake completed1.52 s
22 days agoHandshake completed680 ms
25 days agoHandshake completed1.58 s

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

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 JiZhiMCP and makes no claim about it beyond what these checks measured.