_ registry / mcp streamable-http · checked 7m ago

th-recut-cloud-api

https://www.qianshi.cool

Registry code: 612fc03ebd2d2355

api record

输入口播文案与素材,自动生成安全排版出片计划并云端渲染成片。前 3 条免费。

from a public catalogue that lists it, not from the operator

endpoint
https://www.qianshi.cool/thapi/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is th-recut-cloud-api live?
Yes — it answered the hub's last check (checked 7m ago). It answered 100% of checks over the last 30 days.
Is th-recut-cloud-api free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does th-recut-cloud-api have?
3 tools: generate_recut_plan, render_recut_video, get_recut_job.
Is th-recut-cloud-api safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
700ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 auth-required 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_recut_job auth-required 7m ago

    查询渲染任务状态与成片 URL。

    mcp-tool

    {
      "type": "object",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • generate_recut_plan unknown never probed

    根据口播视频元信息与文案,生成出片计划(人脸禁区安全布局 / MG 卡片反选 / BGM 情绪匹配),不渲染。

    mcp-tool

    {
      "type": "object",
      "required": [
        "copy",
        "video"
      ],
      "properties": {
        "copy": {
          "type": "string",
          "description": "口播文案(纯文本或结构化章节)"
        },
        "slug": {
          "type": "string"
        },
        "theme": {
          "type": "string",
          "default": "apple-keynote"
        },
        "video": {
          "type": "object",
          "required": [
            "width",
            "height"
          ],
          "properties": {
            "width": {
              "type": "integer"
            },
            "height": {
              "type": "integer"
            },
            "rotation": {
              "type": "integer"
            },
            "durationSec": {
              "type": "number"
            }
          },
          "description": "视频元信息"
        },
        "zones": {
          "type": "object",
          "description": "可选,客户端人脸禁区探测结果 {available_bands:[{id,x,y,w,h}]}"
        }
      }
    }
    arguments 46 lines
  • render_recut_video unknown never probed

    提交渲染任务,返回 job_id;用 get_recut_job 轮询成片。

    mcp-tool

    {
      "type": "object",
      "required": [
        "media_url"
      ],
      "properties": {
        "copy": {
          "type": "string"
        },
        "plan": {
          "type": "object",
          "description": "可直接传 generate_recut_plan 的结果,跳过重新生成"
        },
        "slug": {
          "type": "string"
        },
        "video": {
          "type": "object"
        },
        "media_url": {
          "type": "string",
          "description": "口播视频素材的公开可下载地址"
        }
      }
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 612fc03ebd2d2355.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/612fc03ebd2d2355/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/612fc03ebd2d2355/badge.svg)](https://brick.blue/agent/612fc03ebd2d2355?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.