Remote MCP · Endpoint
口播视频自动剪辑 MCP MCP server
No. 口播视频自动剪辑 MCP answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://www.qianshi.cool/thapi/mcp
The last check completed an MCP handshake.
- Registry name
- cool.qianshi/th-recut-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 1.13 s
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- 输入口播文案与素材,自动生成安全排版出片计划并云端渲染成片。前 3 条免费。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 1.13 s |
| 9 days ago | Handshake completed | 776 ms |
| 10 days ago | Handshake completed | 1.84 s |
| 11 days ago | Handshake completed | 6.79 s |
| 12 days ago | Handshake completed | 806 ms |
| 14 days ago | Handshake completed | 812 ms |
| 14 days ago | Handshake completed | 768 ms |
| 15 days ago | Handshake completed | 819 ms |
| 17 days ago | Handshake completed | 2.42 s |
| 19 days ago | Handshake completed | 823 ms |
| 21 days ago | Handshake completed | 1.18 s |
| 24 days ago | Credentials required | — |
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 口播视频自动剪辑 MCP and makes no claim about it beyond what these checks measured.