Douyin TikTok Download API — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow API and platform-policy changes that can alter the documented MCP or automation path

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Self-hosted Douyin and TikTok data collection, media retrieval and analysis.

What we know

The project exposes Douyin and TikTok data through a self-hosted API stack with identity management, PostgreSQL storage, REST endpoints, MCP access and a web console.

Maintenance / activity evidence

Observed Oct 2, 2026 (UTC)docs: pin the real build sha in the 5.1.3 release notes

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can retrieve and persist social-platform data through configured identities. Writes: Persist collected data; Download media.
Authentication not yet verified.
Sensitive access: Platform identities/cookies or credentials depending on configuration, Collected user-generated content

The stack can collect, download and persist social-platform content using configured identities; privacy, credential and platform-policy handling need explicit review.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

20,485 repository stars

Stars observed Oct 6, 2026.

All limitations / Review context

Are the documented media endpoints and MCP-facing integration still maintained and attributable?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The stack can collect, download and persist social-platform content using configured identities; privacy, credential and platform-policy handling need explicit review.
Can retrieve and persist social-platform data through configured identities.
Collected platform data can be written to PostgreSQL and local storage.
Reviewed write actions: Persist collected data; Download media
Sensitive access: Platform identities/cookies or credentials depending on configuration, Collected user-generated content
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Exact MCP authentication boundary
Platform behavior and anti-abuse controls can change.
Use must comply with platform terms and applicable privacy rules.

Original activity observations

2026-10-02T00:41:58Z: docs: pin the real build sha in the 5.1.3 release notes

Technical identity

github.com/evil0ctal/douyin_tiktok_download_api

Exact implementation source: https://github.com/evil0ctal/douyin_tiktok_download_api ↗
Reviewed resource type: Gateway
Repository identity: Evil0ctal/Douyin_TikTok_Download_API

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
evil0ctal/douyin_tiktok_download_api
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Warning

Session/cookie handling and third-party platform policies need review.
Do not publish unguarded port or run remote install script without review.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
Not a typical standalone MCP server installation; the product documentation does not establish a universal MCP host setup. Do not infer one.
Installer may modify local system or require credentials; review publisher documentation before running. Multiple publisher-documented README steps combined as an ordered excerpt; not a verbatim single publisher code block.
Review prerequisites, permissions, paths or resulting changes before running.
Take a backup before uninstall; removal and volume/data deletion are separate deliberate choices.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions · Review before use
```
git clone https://github.com/Evil0ctal/Douyin_TikTok_Download_API.git
cd Douyin_TikTok_Download_API
```
Configure / authenticate
Publisher instructions
Follow official Docker Compose install guide before MCP hookup. API includes MCP at http://127.0.0.1:8000/mcp/ (trailing slash mandatory); use an API key with douyin:read/tiktok:read permissions and an authenticated client.
Check connection
Suggested check
Check client MCP tool discovery and read-only station/platform metadata; distinguish 401 auth errors from 307 redirect at /mcp lacking trailing slash.
Remove / uninstall / revoke
MCP100 setup guide
Remove `dtk` MCP client configuration. If retiring the whole dedicated backend, stop the deployment with its documented compose/management command; preserve Postgres/Redis volumes unless explicitly deleting data.

Official Documentation & Sources

What it does

The project exposes Douyin and TikTok data through a self-hosted API stack with identity management, PostgreSQL storage, REST endpoints, MCP access and a web console.

Capability: Search & Web
Resource type: Gateway
Industry: Media & Marketing
Best fit: Self-hosted Douyin and TikTok data collection, media retrieval and analysis.

Representative uses

Retrieve posts, authors and comments
Search Douyin/TikTok data
Download videos and images
Store collected data for later analysis

Limitations

Platform behavior and anti-abuse controls can change.
Use must comply with platform terms and applicable privacy rules.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Can retrieve and persist social-platform data through configured identities.
Data handling: Collected platform data can be written to PostgreSQL and local storage.
Cost: free
Risk and cautions: The stack can collect, download and persist social-platform content using configured identities; privacy, credential and platform-policy handling need explicit review.

Access scope and cautions

Write actions: Persist collected data Download media
Sensitive access: Platform identities/cookies or credentials depending on configuration Collected user-generated content
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Retrieve posts, authors and comments; Search Douyin/TikTok data; Download videos and images; Store collected data for later analysis.

Can it modify data or perform write operations?

Documented write actions include: Persist collected data; Download media. Recorded permission boundary: Can retrieve and persist social-platform data through configured identities.

What data-handling boundary should I consider?

Collected platform data can be written to PostgreSQL and local storage. Recorded sensitive-access context: Platform identities/cookies or credentials depending on configuration; Collected user-generated content.

What limitations and risks should I check before use?

The stack can collect, download and persist social-platform content using configured identities; privacy, credential and platform-policy handling need explicit review. Platform behavior and anti-abuse controls can change. Use must comply with platform terms and applicable privacy rules. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

Evil0ctal is listed as Community implementation in MCP100’s current evidence.