口播视频自动剪辑 MCP server
cool.qianshi/th-recut-mcpqianshi.coolstreamable-httpv1.2.0Scanned
输入口播文案与素材,自动生成安全排版出片计划并云端渲染成片。前 3 条免费。
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.
What the 口播视频自动剪辑 MCP server can do
The 口播视频自动剪辑 MCP server is published by qianshi.cool, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: generate_recut_plan and render_recut_video), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (get_recut_job).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
generate_recut_plan根据口播视频元信息与文案,生成出片计划(人脸禁区安全布局 / MG 卡片反选 / BGM 情绪匹配),不渲染。No findings
Why it is in this group
- The name "generate_recut_plan" says "generate": a word for a change.
Description, as the server wrote it 根据口播视频元信息与文案,生成出片计划(人脸禁区安全布局 / MG 卡片反选 / BGM 情绪匹配),不渲染。
render_recut_video提交渲染任务,返回 job_id;用 get_recut_job 轮询成片。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 提交渲染任务,返回 job_id;用 get_recut_job 轮询成片。
Only reads 1Show 1 read-only tool
get_recut_job查询渲染任务状态与成片 URL。Reads text others writeNo findings
Why it is in this group
- The name "get_recut_job" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 查询渲染任务状态与成片 URL。
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:51 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.qianshi.cool/.well-known/oauth-protected-resource/thapi/mcp
- Authorization servers
- https://www.qianshi.cool/ViralForge
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.qianshi.cool/thapi/mcp: tools/list returned 3 tools to an anonymous client, including generate_recut_plan (write), render_recut_video (write)
Posture changes
- Nov 20, 2026
- RFC 9728 protected resource metadata: none to https://www.qianshi.cool/.well-known/oauth-protected-resource/thapi/mcp
- Authorization servers: none to https://www.qianshi.cool/ViralForge
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to no
- Oct 29, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-03-26
- WWW-Authenticate on 401: yes to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://www.qianshi.cool/.well-known/oauth-protected-resource/thapi/mcp; Authorization servers: none -> https://www.qianshi.cool/ViralForge; Dynamic client registration: …View diff
- RFC 9728 protected resource metadata: none to https://www.qianshi.cool/.well-known/oauth-protected-resource/thapi/mcp
- Authorization servers: none to https://www.qianshi.cool/ViralForge
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to no
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 2 (and 2 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-03-26
- WWW-Authenticate on 401: yes to not observed
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http th-recut https://www.qianshi.cool/thapi/mcpclaude mcp add --transport http th-recut https://www.qianshi.cool/thapi/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__th-recut__get_recut_job"
],
"ask": [
"mcp__th-recut__generate_recut_plan",
"mcp__th-recut__render_recut_video"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as th-recut. Review it before you use it.
Capability tags behind 1 rule
- mcp__th-recut__get_recut_job untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/cool.qianshi/th-recut-mcp/verify?hash=cf13adc5d70a487357c81d70df8855bee608c3d46a6fa00b45da36ab5d4f66ee" | jq -e '.changed == false'Pinned hash cf13adc5d70a, from Nov 9, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/cool.qianshi/th-recut-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/cool.qianshi/th-recut-mcp)Source: MCP Registry · repository. Synced Oct 28, 2026, 08:17 UTC.
口播视频自动剪辑 MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the 口播视频自动剪辑 MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the 口播视频自动剪辑 MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the 口播视频自动剪辑 MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the 口播视频自动剪辑 MCP server have?
- 3 tools: 2 write, 1 read. generate_recut_plan, render_recut_video and get_recut_job.
Does the 口播视频自动剪辑 MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the 口播视频自动剪辑 MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the 口播视频自动剪辑 MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.