_ registry / mcp streamable-http · checked 3h ago

DouParse 视频解析

https://www.qiaiwan.top

Registry code: 7f81b2b0def2922d

api record

抖解 DouParse 视频解析工具。支持抖音、快手、小红书、哔哩哔哩、微信视频号、微博、知乎等 10+ 平台：把用户给的分享链接/分享文本交给 parse_video，即可拿到无水印视频直链、图集图片直链、背景音乐直链与文案。需要 API Key（在 https://www.qiaiwan.top/account 注册领取），配置在 MCP 客户端的 Authorization: Bearer 头里。仅真实解析成功扣 1 次，缓存命中/失败不扣。

endpoint
https://www.qiaiwan.top/mcp/
protocol
streamable-http ·2025-06-18
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 DouParse 视频解析 live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is DouParse 视频解析 free to use?
Yes — the hub reached it with no key and no payment.
What tools does DouParse 视频解析 have?
3 tools: redeem_code, parse_video, get_balance.
Is DouParse 视频解析 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
752ms

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 open 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_balance open 3h ago

    查询当前 API Key 的剩余调用次数、每分钟限频、今日已用次数与状态。

    mcp-tool

    {
  "type": "object",
  "title": "get_balanceArguments",
  "properties": {}
}
    arguments 5 lines
  • redeem_code unknown never probed

    用充值码给账号加调用次数（一码一用）。 Args: code: 后台/发卡平台发放的充值码。

    mcp-tool

    {
  "type": "object",
  "title": "redeem_codeArguments",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "title": "Code"
    }
  }
}
    arguments 13 lines
  • parse_video unknown never probed

    解析短视频/图文分享链接，返回无水印直链。 支持平台：抖音、快手、小红书、哔哩哔哩、微信视频号、微博、知乎等。 参数 url 可以是分享文本（含口令的整段文字）、短链（如 https://v.douyin.com/xxx/） 或完整链接。返回字段见下：视频类看 video_url / qualities，图集类看 images， 背景音乐看 music_url。所有直链均为平台 CDN 地址，请自行下载（有时效，过期重解析）。 Args: url: 分享文本、短链或完整视频/图文链接。

    mcp-tool

    {
  "type": "object",
  "title": "parse_videoArguments",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "title": "Url"
    }
  }
}
    arguments 13 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 7f81b2b0def2922d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7f81b2b0def2922d/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/7f81b2b0def2922d/badge.svg)](https://brick.blue/agent/7f81b2b0def2922d?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.