Remote MCP · Endpoint
中国 AI 合规与备案（条文级自查） MCP server
No. 中国 AI 合规与备案（条文级自查） answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://savantcat.cn/mcp-compliance
The last check completed an MCP handshake.
- Registry name
- cn.savantcat/ai-compliance
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 2.59 s
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 生成式AI备案、AI生成内容标识、深度合成、算法备案：条文级问答 + 应办事项清单（中文）
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 2.59 s |
| 1 day ago | Handshake completed | 3.92 s |
| 2 days ago | Failed - the request timed out | — |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 3.
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 中国 AI 合规与备案（条文级自查） and makes no claim about it beyond what these checks measured.