Video Downloader MCP server

EasyDown exposes a video downloader MCP endpoint at https://api.easydown.org/mcp.

API authentication

Send the token in the Authorization header. Never place production tokens in URLs, client logs, source control, or analytics.

Successful parses are charged by platform. Most other supported platforms: 1 credit; YouTube: 3 credits; Threads: 2 credits; Kuaishou / Kwai: 2 credits; RedNote / Xiaohongshu: 10 credits. A failed request, empty response, or unavailable post alone does not trigger a charge. A no-media request is charged only when both a processing cost and a clear content restriction are confirmed. This exception currently applies to Douyin and Toutiao only. Unsupported URLs, input validation failures, invalid or unauthorized API tokens, temporary failures, timeouts, and unexplained empty results cost 0 credits. Unavailable content without a confirmed processing cost is also free.

REST and MCP use the same platform rates and confirmed content-restriction exception. MCP returns the actual charge in billing.creditsCharged, including on a failed result.

Do not infer a zero charge from an HTTP error, data: null, or the content_unavailable code. If a billing header is missing or the connection is interrupted, the charge is unknown: check dashboard usage records before resubmitting.

Full billing rules and charge checks

Limits and behavior

• Keep the token in the MCP client's secure secret store.
• Do not place it in prompts, tool arguments, URLs, or shared configuration files.
• REST and MCP requests use the same platform rates and confirmed content-restriction exception.