Remote MCP · Endpoint
550W AI 去字幕去水印（国内） MCP server
No — it is up, but it requires credentials. 550W AI 去字幕去水印（国内） answered 2 hours ago with an authentication challenge rather than a session.
Auth requiredLast checked 2 hours ago
Server URL
https://www.550wai.cn/mcp/cn
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- cn.550wai/550w-ai-media-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
- 通过网页 OAuth 授权，使用 550W AI 处理视频硬字幕、视频水印和图片水印，并查询任务进度与账户积分。媒体处理按账户现有积分价格计费。
- Website
- https://qzm.550wai.cn/agent/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Credentials required | — |
| 1 day ago | Credentials required | — |
| 2 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 550W AI 去字幕去水印（国内） and makes no claim about it beyond what these checks measured.