Remote MCP · Endpoint
可灵 AI(中国区) / Kling AI (China) MCP server
No — it is up, but it requires credentials. 可灵 AI(中国区) / Kling AI (China) answered 5 hours ago with an authentication challenge rather than a session.
Auth requiredLast checked 5 hours ago
Server URL
https://klingai.com/mcp/plugin
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- io.github.klingai-dev/kling-ai-cn
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 可灵 AI 中国区:通过 OAuth 连接国内账号,生成图片和视频、查询任务与积分。生成消耗该账号的积分。
- Website
- https://klingai.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Credentials required | — |
| 4 days ago | Credentials required | — |
| 7 days ago | Credentials required | — |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 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(中国区) / Kling AI (China) and makes no claim about it beyond what these checks measured.