SocialDataX YouTube MCP
REMOTE · MCP.SOCIALDATAX.COM · SCANNED SEP 20
YouTube public video, comment, reply, channel, search, and speech-to-text transcript tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2229 tokens (~185/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SocialDataX YouTube MCP server?
SocialDataX YouTube MCP is a hosted endpoint at https://mcp.socialdatax.com/youtube/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.socialdatax.com
claude mcp add --transport http com-52choujiang-youtube-insights 'https://mcp.socialdatax.com/youtube/mcp'
{
"mcpServers": {
"com-52choujiang-youtube-insights": {
"url": "https://mcp.socialdatax.com/youtube/mcp"
}
}
} {
"servers": {
"com-52choujiang-youtube-insights": {
"type": "http",
"url": "https://mcp.socialdatax.com/youtube/mcp"
}
}
} [mcp_servers.com-52choujiang-youtube-insights] url = "https://mcp.socialdatax.com/youtube/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-52choujiang-youtube-insights": {
"type": "remote",
"url": "https://mcp.socialdatax.com/youtube/mcp",
"enabled": true
}
}
} openclaw mcp add com-52choujiang-youtube-insights --url 'https://mcp.socialdatax.com/youtube/mcp' --transport streamable-http
mcp_servers:
com-52choujiang-youtube-insights:
url: "https://mcp.socialdatax.com/youtube/mcp" {
"McpServers": {
"com-52choujiang-youtube-insights": {
"Transport": "http",
"Url": "https://mcp.socialdatax.com/youtube/mcp"
}
}
} assistant mcp add com-52choujiang-youtube-insights -t streamable-http -u 'https://mcp.socialdatax.com/youtube/mcp'
{
"mcpServers": {
"com-52choujiang-youtube-insights": {
"type": "http",
"url": "https://mcp.socialdatax.com/youtube/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “socialdatax_get_points_balance” rewrote its description, which is the text the model reads security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.socialdatax.com/youtube/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.socialdatax.com | CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN | 30 Jun 2026 | 28 Sept 2026 | RSA 2048 | SHA256-RSA | 8e8caa5cf3d2f797fec12571ba1ea84b323016 |
| SANs: mcp.socialdatax.com | ||||||
| CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN | 15 May 2024 | 15 May 2034 | RSA 4096 | SHA384-RSA | 1c9e6b412deb0a85461de03dbe30984d0573888b |
| CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL | 7 Oct 2025 | 14 Jan 2029 | RSA 4096 | SHA384-RSA | b2dc4c34932d709cd4bf0b099401695c |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.socialdatax.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| socialdatax.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="missing_api_key", error_description="API Key required"
Bearer error="missing_api_key", error_description="API Key required" Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.socialdatax.com/youtube/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.socialdatax.com/youtube/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
socialdatax_get_points_balance ~53
查询当前 API Key 账户的 SocialDataX 积分余额、剩余积分或点数 / remaining points balance。需要充值时请访问 https://socialdatax.com/dashboard/billing。
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
youtube_get_channel_info_by_url ~129
根据 YouTube 频道主页链接获取频道资料。
| Name | Type | Req | Description |
|---|---|---|---|
| channel_url | string | yes | YouTube 频道主页链接;支持 https://www.youtube.com/@用户名、/channel/、/c/ 和 /user/ 链接形态。如果传入频道 tab 子页链接,会规范化到对应的 https://www.youtube.com/... 频道主页。从搜索、详情、评论或评论回复结果读取频道资料时,直接传 author.profile_url;不要传 channel_id、裸 @用… |
| Name | Type | Req | Description |
|---|---|---|---|
| avatar_url | – | yes | 频道头像链接;不可用时为 null。 |
| banner_url | – | yes | 频道横幅图链接;不可用时为 null。 |
| bio | string | yes | 频道简介;不可用时为空字符串。 |
| channel_id | string | yes | YouTube 频道 ID;用于识别和去重。 |
| country | string | yes | 频道公开国家或地区;不可用时为空字符串。 |
| external_links | array | yes | 频道主页外链列表;无外链时为空数组。 |
| follower_count | – | yes | 订阅者数量;可能为近似值;不可用时为 null。 |
| name | string | yes | 频道名称;不可用时为空字符串。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
| posted_video_count | – | yes | 频道视频数量;不可用时为 null。 |
| profile_url | – | yes | 频道主页链接;不可用时为 null。 |
| verified | boolean | yes | 频道是否有认证标识。 |
| view_count | – | yes | 频道累计观看次数;不可用时为 null。 |
No examples provided.
youtube_get_user_posted_videos_by_channel_url ~328
根据 YouTube 频道主页链接获取频道发布视频或 Shorts 列表。
| Name | Type | Req | Description |
|---|---|---|---|
| channel_url | string | yes | YouTube 频道主页链接;支持 https://www.youtube.com/@用户名、/channel/、/c/ 和 /user/ 链接形态。如果传入频道 tab 子页链接,会规范化到对应的 https://www.youtube.com/... 频道主页。从搜索、详情、评论、评论回复或频道资料结果读取作者发布视频或 Shorts 时,直接传 author.profile_url 或 p… |
| page_token | string | – | YouTube 频道发布列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一频道、同一 video_type 的视频续页;更换频道或 video_type 时,请清空 page… |
| video_type | string | – | 频道发布视频类型:video=频道“视频”tab,short=频道 Shorts tab。默认 video。当前不支持 live、course 或 playlist。更换 video_type 时,请清空 page_token 后从第一页重新读取。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页 YouTube 频道发布视频或 Shorts 列表;当前页可能为空,是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页频道发布列表不透明分页令牌;为空表示没有更多视频。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;只用于同一频道、同一 video_type 的视频续页;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
youtube_get_video_comment_replies ~332
根据 reply_token 获取 YouTube 评论回复;用户已提供有效 reply_token 时直接使用;已有 YouTube 视频链接但缺少 reply_token 时,调用 youtube_get_video_comments_by_url 获取一级评论;缺少视频定位信息时向用户索取;不要传一级评论或回复项的 comment_id;支持 page_token 翻页。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | YouTube 评论回复分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一 reply_token 对应的评论回复续页;更换 reply_token 时,请清空 page_tok… |
| reply_token | string | yes | 读取某条 YouTube 视频一级评论回复所需的不透明令牌;用户已提供时直接原样使用;否则从 youtube_get_video_comments_by_url 返回的 items[*].reply_token 原样复制。只有有效且非空的 reply_token 才调用本工具;不要传 comment_id、video_url、video_id、频道链接、播放列表链接或搜索页链接。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页 YouTube 评论回复列表;当前页可能为空,是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页评论回复不透明分页令牌;为空表示没有更多评论回复。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;只用于同一 reply_token 对应的评论回复续页;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
youtube_get_video_comments_by_url ~264
根据 YouTube 视频链接获取公开视频一级评论。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | YouTube 视频评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一视频和同一 sort_type 的评论续页;更换视频或 sort_type 时,请清空 page_tok… |
| sort_type | string | – | 评论排序方式:hot=热门评论,time_descending=较新评论优先。YouTube 可能保留作者评论或置顶评论在当前页前部;如无明确排序需求,保持 hot。 |
| video_url | string | yes | YouTube 视频页面链接;支持 watch、youtu.be 短链和 Shorts 链接。从搜索结果读取评论时,直接传搜索结果里的 share_url(items[*].share_url);不要传频道链接、播放列表链接、搜索页链接或裸 video_id。 |
| Name | Type | Req | Description |
|---|---|---|---|
| comment_count | – | yes | 评论总数;不是当前页 items 数量;不可用时为 null。 |
| items | array | yes | 当前页 YouTube 视频一级评论列表;当前页可能为空,是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页评论不透明分页令牌;为空表示没有更多评论。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;只用于当前 YouTube 视频和同一 sort_type 的评论续页;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
youtube_get_video_detail_by_url ~86
根据 YouTube 视频链接获取公开视频详情。
| Name | Type | Req | Description |
|---|---|---|---|
| video_url | string | yes | YouTube 视频页面链接;支持 watch、youtu.be 短链和 Shorts 链接。从搜索结果读取详情时,直接传搜索结果里的 share_url(items[*].share_url);不要传频道链接、播放列表链接、搜索页链接或裸 video_id。 |
| Name | Type | Req | Description |
|---|---|---|---|
| author | object | yes | 作者或频道信息。 |
| comment_count | – | yes | 评论数;不可用时为 null。 |
| cover_image_url | – | yes | 视频封面或缩略图链接;不可用时为 null。 |
| description | string | yes | 视频详情页完整描述文本;不是摘要或视频转写;不可用时为空字符串。 |
| duration_ms | – | yes | 视频时长,单位毫秒;不可用时为 null。 |
| like_count | – | yes | 点赞数;不可用时为 null。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
| publish_time | string | yes | 发布时间,ISO 8601 时间字符串;不可用时为空字符串。 |
| share_url | string | yes | 可打开或分享的 YouTube 视频页面链接;不是视频播放资源链接。 |
| title | string | yes | 视频标题;不可用时为空字符串。 |
| topic_tags | array | yes | 视频关键词或话题标签;无数据时为空数组。 |
| video_id | string | yes | YouTube 视频 ID;用于识别和去重。 |
| view_count | – | yes | 观看次数;不可用时为 null。 |
No examples provided.
youtube_get_video_speech_text_job ~99
根据用户提供的有效 job_id,或 submit 工具返回的 job_id 查询 YouTube 视频口播转文字任务状态;每次最多等待 240 秒,不触发重处理,也不要重复提交任务。
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | 口播转文字任务 ID;用户已提供时直接使用,否则使用 YouTube submit 工具返回的 job_id;不要传 video_id 或视频链接。 |
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | 平台内容 ID。 |
| content_meta | object | yes | 作品上下文信息,便于结合转写内容做口播分析。 |
| content_type | string | yes | 内容类型。 |
| error | – | yes | 失败或过期时的稳定错误结构;非终态或成功时为 null。 |
| is_terminal | boolean | yes | 是否已终态。 |
| job_id | string | yes | 任务 ID。 |
| message | string | yes | 面向用户/AI 的状态说明。 |
| next_action | – | yes | 非终态时建议的下一步查询动作。 |
| next_poll_after_seconds | – | yes | 建议下次查询前等待的秒数;非终态时可用。 |
| platform | string | yes | 任务所属平台。 |
| source_id | string | yes | 任务来源 ID。 |
| status | string | yes | 任务状态。 |
| transcript | – | yes | 成功时的口播转文字结果;非终态或失败时为 null。 |
No examples provided.
youtube_search_videos ~566
按搜索词搜索 YouTube 公开视频,只返回视频结果。用户需要按搜索词查找视频时使用;已有视频、Shorts 或 youtu.be 链接时使用视频详情或评论工具;已有频道主页链接时使用频道资料或频道发布视频工具;不支持播放列表链接作为搜索输入;支持筛选和 page_token 翻页。
| Name | Type | Req | Description |
|---|---|---|---|
| duration_range | string | – | 视频时长筛选:all=不限,under_4_min=4 分钟以内,between_4_and_20_min=4 到 20 分钟,over_20_min=20 分钟以上。只对视频类搜索结果有意义;如无明确时长需求,保持 all。 |
| keyword | string | yes | YouTube 视频搜索词,可传关键词或短语,例如品牌名、话题、人物名或内容需求;不要传 YouTube 视频链接、Shorts 链接、频道链接、播放列表链接、video_id 或 page_token。 |
| page_token | string | – | YouTube 搜索分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一关键词、排序和筛选链路;更换关键词、排序、视频类型、发布时间或时长筛选时,请清空 page_token 后从… |
| publish_time_range | string | – | 发布时间筛选:all=不限,last_hour=过去 1 小时,today=今天,this_week=本周,this_month=本月,this_year=今年。如无明确发布时间需求,保持 all。 |
| sort_type | string | – | 排序方式:general=相关性,time_descending=最新上传,view_count_descending=观看次数最多,rating=评分较高。如无明确排序需求,保持 general。 |
| video_type | string | – | 视频类型筛选:all=不限类型,video=普通视频,movie=电影。all 会保留视频类搜索结果,输出项用 video_type 标记可明确识别的类型。可明确识别的 Shorts 会标为 short,其余视频结果标为 video。当前不支持 channel、short 或 playlist 作为筛选项;频道信息只作为视频作者信息返回。movie 是筛选条件,返回项使用同一搜索结果字段,并以… |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页 YouTube 搜索结果列表;当前页可能为空,是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页不透明分页令牌;为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;只用于当前 YouTube 搜索续页;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
youtube_submit_video_speech_text_by_url ~114
提交 YouTube 视频口播转文字任务;提交后最多等待 240 秒,未完成时返回 job_id 和下一步查询动作。
| Name | Type | Req | Description |
|---|---|---|---|
| video_url | string | yes | YouTube 视频页面链接;支持 watch、youtu.be 短链和 Shorts 链接。从搜索结果提交口播转文字任务时,直接传搜索结果里的 share_url(items[*].share_url);不要传频道链接、播放列表链接、搜索页链接或裸 video_id。 |
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | 平台内容 ID。 |
| content_meta | object | yes | 作品上下文信息,便于结合转写内容做口播分析。 |
| content_type | string | yes | 内容类型。 |
| error | – | yes | 失败或过期时的稳定错误结构;非终态或成功时为 null。 |
| is_terminal | boolean | yes | 是否已终态。 |
| job_id | string | yes | 任务 ID。 |
| message | string | yes | 面向用户/AI 的状态说明。 |
| next_action | – | yes | 非终态时建议的下一步查询动作。 |
| next_poll_after_seconds | – | yes | 建议下次查询前等待的秒数;非终态时可用。 |
| platform | string | yes | 任务所属平台。 |
| source_id | string | yes | 任务来源 ID。 |
| status | string | yes | 任务状态。 |
| transcript | – | yes | 成功时的口播转文字结果;非终态或失败时为 null。 |
No examples provided.
youtube_submit_video_speech_text_by_video_id ~94
根据 YouTube video_id 提交口播转文字任务;提交后最多等待 240 秒,未完成时返回 job_id 和下一步查询动作。
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | YouTube 视频 ID,必须是 11 位字符串;可直接使用搜索结果 items[*].video_id。不要传视频链接、频道链接、播放列表链接或搜索页链接。 |
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | 平台内容 ID。 |
| content_meta | object | yes | 作品上下文信息,便于结合转写内容做口播分析。 |
| content_type | string | yes | 内容类型。 |
| error | – | yes | 失败或过期时的稳定错误结构;非终态或成功时为 null。 |
| is_terminal | boolean | yes | 是否已终态。 |
| job_id | string | yes | 任务 ID。 |
| message | string | yes | 面向用户/AI 的状态说明。 |
| next_action | – | yes | 非终态时建议的下一步查询动作。 |
| next_poll_after_seconds | – | yes | 建议下次查询前等待的秒数;非终态时可用。 |
| platform | string | yes | 任务所属平台。 |
| source_id | string | yes | 任务来源 ID。 |
| status | string | yes | 任务状态。 |
| transcript | – | yes | 成功时的口播转文字结果;非终态或失败时为 null。 |
No examples provided.
What is the SocialDataX YouTube MCP server?
SocialDataX YouTube MCP is listed in the public MCP registry as com.52choujiang/youtube-insights. YouTube public video, comment, reply, channel, search, and speech-to-text transcript tools. This page covers its hosted endpoint (https://mcp.socialdatax.com/youtube/mcp).
Is the SocialDataX YouTube MCP server safe to use?
SocialDataX YouTube MCP scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SocialDataX YouTube MCP server expose?
SocialDataX YouTube MCP exposes 10 tools: youtube_search_videos, youtube_get_video_detail_by_url, youtube_get_channel_info_by_url, youtube_get_user_posted_videos_by_channel_url, youtube_get_video_comments_by_url, and 5 more. Their descriptions and schemas cost roughly 2,065 tokens of context every time the server is loaded.
Does the SocialDataX YouTube MCP server require authentication?
Yes. SocialDataX YouTube MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SocialDataX YouTube MCP server still maintained?
SocialDataX YouTube MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.