TikTok Unauthorized API Scraper
# Tiktok Unauthorized Api Scraper No Watermark Analytics Feed MCP Server
[English](./README_EN.md) | 简体中文 | [繁體中文](./README_ZH-TW.md)
用于访问 Tiktok Unauthorized Api Scraper No Watermark Analytics Feed API 的 MCP 服务器。
## 🚀 使用 EMCP 平台快速体验
**[EMCP](https://sit-emcp.kaleido.guru)** 是一个强大的 MCP 服务器管理平台,让您无需手动配置即可快速使用各种 MCP 服务器!
### 快速开始:
1. 🌐 访问 **[EMCP 平台](https://sit-emcp.kaleido.guru)**
2. 📝 注册并登录账号
3. 🎯 进入 **MCP 广场**,浏览所有可用的 MCP 服务器
4. 🔍 搜索或找到本服务器(`bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed`)
5. 🎉 点击 **"安装 MCP"** 按钮
6. ✅ 完成!即可在您的应用中使用
### EMCP 平台优势:
- ✨ **零配置**:无需手动编辑配置文件
- 🎨 **可视化管理**:图形界面轻松管理所有 MCP 服务器
- 🔐 **安全可靠**:统一管理 API 密钥和认证信息
- 🚀 **一键安装**:MCP 广场提供丰富的服务器选择
- 📊 **使用统计**:实时查看服务调用情况
立即访问 **[EMCP 平台](https://sit-emcp.kaleido.guru)** 开始您的 MCP 之旅!
---
## 简介
这是一个 MCP 服务器,用于访问 Tiktok Unauthorized Api Scraper No Watermark Analytics Feed API。
- **PyPI 包名**: `bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed`
- **版本**: 1.0.0
- **传输协议**: stdio
## 安装
### 从 PyPI 安装:
```bash
pip install bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed
```
### 从源码安装:
```bash
pip install -e .
```
## 运行
### 方式 1: 使用 uvx(推荐,无需安装)
```bash
# 运行(uvx 会自动安装并运行)
uvx --from bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed bach_tiktok_unauthorized_api_scraper_no_watermark_analytics_feed
# 或指定版本
uvx --from bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed@latest bach_tiktok_unauthorized_api_scraper_no_watermark_analytics_feed
```
### 方式 2: 直接运行(开发模式)
```bash
python server.py
```
### 方式 3: 安装后作为命令运行
```bash
# 安装
pip install bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed
# 运行(命令名使用下划线)
bach_tiktok_unauthorized_api_scraper_no_watermark_analytics_feed
```
## 配置
### API 认证
此 API 需要认证。请设置环境变量:
```bash
export API_KEY="your_api_key_here"
```
### 环境变量
| 变量名 | 说明 | 必需 |
|--------|------|------|
| `API_KEY` | API 密钥 | 是 |
| `PORT` | 不适用 | 否 |
| `HOST` | 不适用 | 否 |
### 在 Cursor 中使用
编辑 Cursor MCP 配置文件 `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed": {
"command": "uvx",
"args": ["--from", "bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed", "bach_tiktok_unauthorized_api_scraper_no_watermark_analytics_feed"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}
```
### 在 Claude Desktop 中使用
编辑 Claude Desktop 配置文件 `claude_desktop_config.json`:
```json
{
"mcpServers": {
"bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed": {
"command": "uvx",
"args": ["--from", "bach-tiktok_unauthorized_api_scraper_no_watermark_analytics_feed", "bach_tiktok_unauthorized_api_scraper_no_watermark_analytics_feed"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}
```
## 可用工具
此服务器提供以下工具:
### `get_trending_users_in_specific_country`
Fetch trending users and their most popular post for target country passed as parameter
**端点**: `POST /api/trending_users`
---
### `get_trending_hashtags_for_specific_country`
Endpoint search for trending hashtags for specific country passed as the parameter
**端点**: `POST /api/trending_hashtags`
---
### `find_user_by_sec_user_id_fetch_profile_info_fetch_user_posts`
Endpoint does a sequence of actions under the hood: 1. fetches user stats (total likes, followers, subscriptions, etc.) 2. fetch \
**端点**: `POST /api/search_by_sid`
**参数**:
- `X-Fields` (string): An optional fields mask
---
### `build_request_to_find_post_by_link_or_aweme_id`
**Note**: endpoints ending \
**端点**: `POST /api/post_build_request`
**参数**:
- `X-Fields` (string): An optional fields mask
---
### `build_request_to_find_users_posts_by_sec_user_id`
**Note**: endpoints ending \
**端点**: `POST /api/posts_by_sid_build_request`
**参数**:
- `X-Fields` (string): An optional fields mask
---
### `build_request_to_find_user_and_his_info_by_sec_user_id`
**Note**: endpoints ending \
**端点**: `POST /api/search_by_sid_build_request`
**参数**:
- `X-Fields` (string): An optional fields mask
---
### `find_post_by_link_or_aweme_id_fetch_cover_links_metrics_download_links`
Find post data (cover links, metrics, download links, etc.) by post identifier. Takes any of the following post identifiers: - aweme_id - share_link - web_link - short_link If you mix up link type endpoint will work incorrectly!
**端点**: `POST /api/post`
**参数**:
- `X-Fields` (string): An optional fields mask
---
### `find_liked_posts_by_sec_user_id`
Search for post user previously liked (only it the target user allowed this feature in privacy settings)
**端点**: `POST /api/liked`
**参数**:
- `X-Fields` (string): An optional fields mask
---
### `find_user_by_username_fetch_profile_info_fetch_user_posts_full`
Endpoint does a sequence of actions under the hood: 1. finds user by \
**端点**: `POST /api/search_full`
**参数**:
- `X-Fields` (string): An optional fields mask
---
### `find_user_by_username_fetch_profile_info_fetch_user_posts_simplified`
Endpoint does a sequence of actions under the hood: 1. finds user by \
**端点**: `POST /api/search`
**参数**:
- `X-Fields` (string): An optional fields mask
---
## 技术栈
- **传输协议**: stdio
- **HTTP 客户端**: httpx
## 许可证
MIT License - 详见 [LICENSE](./LICENSE) 文件。
## 开发
此服务器由 [API-to-MCP](https://github.com/BACH-AI-Tools/api-to-mcp) 工具生成。
版本: 1.0.0
TDQS
Scored across 10 tools
The tools have overlapping purposes that could cause confusion, such as multiple tools for finding users (e.g., find_user_by_sec_user_id_fetch_profile_info_fetch_user_p, find_user_by_username_fetch_profile_info_fetch_user_post, and find_user_by_username_fetch_profile_info_fetch_user_post_2) with unclear distinctions. However, descriptions help differentiate some tools, like find_liked_posts_by_sec_user_id for liked posts versus find_post_by_link_or_aweme_id_fetch_cover_links_metrics_ for post data.
Naming is inconsistent with mixed conventions: some tools use snake_case with verbs like 'find' or 'get' (e.g., find_user_by_username_fetch_profile_info_fetch_user_post), while others have overly verbose names that deviate from a clear pattern (e.g., build_request_to_find_post_by_link_or_aweme_id). There is no uniform verb_noun structure, making the set chaotic and hard to predict.
With 10 tools, the count is well-scoped for a TikTok scraper, covering key areas like user lookup, post retrieval, trending content, and liked posts. Each tool appears to serve a distinct purpose in the domain, making the number appropriate without being excessive or insufficient.
The tool surface covers core scraping functionalities for TikTok, including user and post lookup, trending data, and liked posts, with minor gaps such as potential missing operations for comment retrieval or direct messaging. Agents can likely work around these gaps, as the set supports essential workflows for data extraction.