Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Finewisdom 社媒与电商数据接口

REMOTE · FINEWISDOM.TOP

统一 Token 调用 103 个社媒与电商数据接口,覆盖抖音、小红书、TikTok、Instagram、YouTube、X、淘宝、京东等 15 个平台。按次 ¥0.1–0.3,成功才计费。

Available components

0 this week 69 Trust /100

Last scanned (12 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 15176 tokens (~147/item across 103 items; 103 tools + 0 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 Management8
  • Stability check failed: schema churn in the 30 days we've observed: 27 tool removals, 1 breaking changes, 0 auth/transport breaks, 100 additions. See how to fix → Fail
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 103 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 104 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “douyin_product_detail” rewrote its description, which is the text the model reads security
    • Tool “douyin_video_like_count” rewrote its description, which is the text the model reads security
    • Tool “douyin_video_play_count” rewrote its description, which is the text the model reads security
    • Tool “jd_comments” rewrote its description, which is the text the model reads security
    • Tool “taobao_item_get” rewrote its description, which is the text the model reads security
    • Tool “taobao_original_detail” rewrote its description, which is the text the model reads security
    • New tool “douyin_author_search” functional
    • New tool “douyin_product_detail_v2” functional
    • New tool “douyin_product_detail_v3” functional
  • 18 Nov 26 0
    • New tool “tiktok_shop_categories” functional
    • New tool “tiktok_shop_category_products” functional
    • New tool “tiktok_shop_hot_products” functional
    • New tool “tiktok_shop_product_detail” functional
    • New tool “tiktok_shop_product_reviews” functional
    • New tool “tiktok_shop_product_search” functional
    • New tool “tiktok_shop_seller_products” functional
  • 17 Nov 26 0
    • Tool “taobao_shop_search” rewrote its description, which is the text the model reads security
    • “taobao_shop_search” added an optional parameter “shop_name” cosmetic
    • “taobao_shop_search” reworded the description of “page” cosmetic
    • “taobao_shop_search” reworded the description of “seller_id” cosmetic
    • “taobao_shop_search” reworded the description of “shop_id” cosmetic
  • 11 Nov 26 0
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • Tool “jd_item_desc” was removed ▼ security
    • Tool “taobao_item_desc” was removed ▼ security
    • New tool “channels_search_videos” functional
    • New tool “wechat_mp_account_articles” functional
    • New tool “wechat_mp_account_profile” functional
    • New tool “wechat_mp_article_comments” functional
    • New tool “wechat_mp_article_detail” functional
  • 10 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “jd_comments_v2” functional
  • 9 Nov 26 0
    • A breaking change shipped without a version bump: still 2.0.0 ▼ security
    • Tool “douyin_product_keyword_search” rewrote its description, which is the text the model reads security
    • Tool “ig_post_comments” rewrote its description, which is the text the model reads security
    • Tool “jd_item_desc” rewrote its description, which is the text the model reads security
    • Tool “taobao_item_desc” rewrote its description, which is the text the model reads security
    • Tool “tw_user_posts” rewrote its description, which is the text the model reads security
    • “ig_post_comments” added a required parameter “code”, so existing callers break ▼ functional
    • “xhs_user_notes” added a required parameter “userid”, so existing callers break ▼ functional
    • “ig_post_comments” dropped the required parameter “media_id” ▼ functional
    • “xhs_user_notes” dropped the required parameter “user_id” ▼ functional
    • “ig_post_comments” added an optional parameter “min_id” cosmetic
    • “tw_user_posts” added an optional parameter “cursor” cosmetic
    • “tw_user_posts” added an optional parameter “rest_id” cosmetic
    • “douyin_product_keyword_search” reworded the description of “count” cosmetic
    • “douyin_product_keyword_search” reworded the description of “page” cosmetic
    • “tw_user_posts” made “screen_name” optional cosmetic
  • 7 Nov 26 −3
    • Stability: pass → fail ▼ security
    • Tool “bili_video” was removed ▼ security
    • Tool “channels_comments” was removed ▼ security
    • Tool “channels_video” was removed ▼ security
    • Tool “company_1688” was removed ▼ security
    • Tool “douyin_author” was removed ▼ security
    • Tool “douyin_product” was removed ▼ security
    • Tool “douyin_search” was removed ▼ security
    • Tool “douyin_video” was removed ▼ security
    • Tool “ecommerce_comments” was removed ▼ security
    • Tool “ecommerce_item” was removed ▼ security
    • Tool “ecommerce_shop” was removed ▼ security
    • Tool “ig_post” was removed ▼ security
    • Tool “img_search_1688” was removed ▼ security
    • Tool “item_1688” was removed ▼ security
    • Tool “ks_video” was removed ▼ security
    • Tool “reviews_1688” was removed ▼ security
    • Tool “search_1688” was removed ▼ security
    • Tool “tiktok_search” was removed ▼ security
    • Tool “tiktok_video” was removed ▼ security
    • Tool “tw_post” was removed ▼ security
    • Tool “weibo_comments” was removed ▼ security
    • Tool “weibo_post” was removed ▼ security
    • Tool “xhs_note” was removed ▼ security
    • Tool “xhs_user” was removed ▼ security
    • Tool “yt_video” was removed ▼ security
    • Tool “zhihu_comments” was removed ▼ security
    • Tool “zhihu_post” was removed ▼ security
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “douyin_video_comments” rewrote its description, which is the text the model reads security
    • Tool “xhs_note_comments” rewrote its description, which is the text the model reads security
    • Tool “xhs_note_search” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • “xhs_note_comments” changed the type of “start”: string → number ▼ functional
    • Tool coverage: 37% → 100% ▲ functional
    • Server version: 1.1.0 → 2.0.0 functional
    • New tool “bili_hot_search” functional
    • New tool “bili_keyword_search” functional
    • New tool “bili_post_comments” functional
    • New tool “bili_post_detail” functional
    • New tool “bili_sub_comments” functional
    • New tool “bili_user_info” functional
    • New tool “bili_user_posts” functional
    • New tool “channels_post_comments” functional
    • New tool “channels_post_detail” functional
    • New tool “channels_search_in_channel” functional
    • New tool “channels_sub_comments” functional
    • New tool “channels_user_info” functional
    • New tool “channels_user_posts” functional
    • New tool “douyin_author_info” functional
    • New tool “douyin_keyword_search” functional
    • New tool “douyin_product_comments” functional
    • New tool “douyin_product_detail” functional
    • New tool “douyin_product_keyword_search” functional
    • New tool “douyin_shop_search” functional
    • New tool “douyin_video_detail” functional
    • New tool “douyin_video_like_count” functional
    • New tool “douyin_video_play_count” functional
    • New tool “ig_keyword_search” functional
    • New tool “ig_post_comments” functional
    • New tool “ig_post_detail” functional
    • New tool “ig_shortcode_to_media_id” functional
    • New tool “ig_sub_comments” functional
    • New tool “ig_user_info” functional
    • New tool “ig_user_posts” functional
    • New tool “item_get_1688” functional
    • New tool “item_get_company_1688” functional
    • New tool “item_review_1688” functional
    • New tool “item_search_1688” functional
    • New tool “item_search_img_1688” functional
    • New tool “jd_comments” functional
    • New tool “jd_item_desc” functional
    • New tool “jd_item_get” functional
    • New tool “jd_shop_search” functional
    • New tool “ks_hot_list” functional
    • New tool “ks_keyword_search” functional
    • New tool “ks_post_comments” functional
    • New tool “ks_post_detail” functional
    • New tool “ks_sub_comments” functional
    • New tool “ks_user_info” functional
    • New tool “ks_user_posts” functional
    • New tool “taobao_comments” functional
    • New tool “taobao_item_desc” functional
    • New tool “taobao_item_get” functional
    • New tool “taobao_original_detail” functional
    • New tool “taobao_shop_search” functional
    • New tool “tiktok_keyword_search” functional
    • New tool “tiktok_post_comments” functional
    • New tool “tiktok_post_detail” functional
    • New tool “tiktok_sub_comments” functional
    • New tool “tiktok_user_info” functional
    • New tool “tiktok_user_posts” functional
    • New tool “tw_keyword_search” functional
    • New tool “tw_post_comments” functional
    • New tool “tw_post_detail” functional
    • New tool “tw_trending” functional
    • New tool “tw_user_info” functional
    • New tool “tw_user_posts” functional
    • New tool “weibo_hot_search” functional
    • New tool “weibo_keyword_search” functional
    • New tool “weibo_post_comments” functional
    • New tool “weibo_post_detail” functional
    • New tool “weibo_sub_comments” functional
    • New tool “weibo_user_info” functional
    • New tool “weibo_user_posts” functional
    • New tool “xhs_note_detail” functional
    • New tool “xhs_sub_comments” functional
    • New tool “xhs_user_info” functional
    • New tool “xhs_user_notes” functional
    • New tool “yt_keyword_search” functional
    • New tool “yt_post_comments” functional
    • New tool “yt_post_detail” functional
    • New tool “yt_sub_comments” functional
    • New tool “yt_user_info” functional
    • New tool “yt_user_posts” functional
    • New tool “zhihu_hot_list” functional
    • New tool “zhihu_keyword_search” functional
    • New tool “zhihu_post_comments” functional
    • New tool “zhihu_post_detail” functional
    • New tool “zhihu_sub_comments” functional
    • New tool “zhihu_user_info” functional
    • New tool “zhihu_user_posts” functional
    • “douyin_video_comments” reworded the description of “_token” cosmetic
    • “xhs_note_comments” reworded the description of “_token” cosmetic
    • “xhs_note_search” reworded the description of “_token” cosmetic
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://finewisdom.top/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.finewisdom.top CN=YR1,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 RSA 2048 SHA256-RSA 6d812048f930d3cf248346a4ca108e06814
SANs: finewisdom.top, www.finewisdom.top
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of finewisdom.top. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
top. DS published 41508 13 Verified
finewisdom.top. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://finewisdom.top/mcp Verified 200
http (plaintext) http://finewisdom.top/mcp HTTPS enforced 301 https://finewisdom.top/mcp
MCP tools · 103 exposed · ~14,973 tokens

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 →

Tool Tokens
taobao_comments ~155

获取淘宝商品评论列表。返回评论正文、点赞数、回复数、评论者昵称与地区、时间戳,按页返回。做评论情感分析、竞品口碑对比或舆情监测时用。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。翻页深度受平台可见范围限制,超出后上游不再返回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
item_idstringyes商品ID
pagenumber–页码(默认 1)

No output schema declared.

No examples provided.

taobao_item_get ~152

获取淘宝商品详情信息,含价格与优惠口径。返回标题、价格与优惠、SKU规格、销量、店铺信息、主图与详情图、库存。做单品价格监控、库存比对时用它;只要标题、主图、规格、不需要券后价时,可用更省事的 taobao_original_detail(券前价)。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
item_idstringyes商品ID

No output schema declared.

No examples provided.

taobao_original_detail ~143

获取淘宝券前详情(不含券后价、券面额、佣金)。只拿标题、主图、SKU 规格等信息时用它;要价格与优惠口径请改用 taobao_item_get。返回标题、价格、SKU规格、销量、店铺信息、主图与详情图、库存。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
item_idstringyes商品ID

No output schema declared.

No examples provided.

taobao_shop_search ~225

搜索淘宝店铺商品列表。返回该店铺在售商品列表,含商品ID、标题、价格、店铺名、类目等(数据源 EveryInfra,page 1~35 约 60 条/页,支持翻页;失败自动回退备用源)。做竞品店铺盘点、在售结构分析时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
pagenumber–页码(1~35,约 60 条/页,默认 1)
seller_idstring–卖家ID(与 shop_id、shop_name 至少提供一个)
shop_idstring–店铺ID(数字ID或店铺链接)
shop_namestring–店铺名称(如:三只松鼠官方旗舰店)

No output schema declared.

No examples provided.

tiktok_keyword_search ~115

TikTok综合搜索。返回视频列表,含每条内容ID与基础互动数据。做关键词监测、内容发现或构建候选集时用,ID可继续调详情与评论接口。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
keywordstringyes关键词

No output schema declared.

No examples provided.

tiktok_post_comments ~165

获取TikTok视频评论。返回评论正文、点赞数、回复数、评论者昵称与地区、时间戳,按页返回。做评论情感分析、竞品口碑对比或舆情监测时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。翻页深度受平台可见范围限制,超出后上游不再返回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
countnumber–数量(默认 20)
cursorstring–游标
item_idstringyes视频ID

No output schema declared.

No examples provided.

tiktok_post_detail ~120

获取TikTok视频详情。返回视频描述、播放/点赞/评论/分享数、作者信息、音乐、发布时间。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
item_idstringyes视频ID

No output schema declared.

No examples provided.

tiktok_shop_categories ~139

获取TikTok商城类目。返回 categories[],每项含 self(category_id、category_name、is_leaf)与 children[]。 支持站点 ID/JP/MX/MY/PH/SG/TH/VN(US/GB/BR 不支持)。单价¥0.2/次,仅成功调用计费。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
regionstring–国家站点 ID/JP/MX/MY/PH/SG/TH/VN(默认 MY)

No output schema declared.

No examples provided.

tiktok_shop_category_products ~186

获取TikTok类目商品。返回 productList[](product_id、标题、主图、价格、销量、评分、店铺)与 hasMore。 支持站点 ID/JP/MX/MY/PH/SG/TH/VN(US/GB/BR 不支持)。单价¥0.2/次,仅成功调用计费。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
category_idstringyes类目ID(取自类目接口)
offsetnumber–起始位置,下一页=本页offset+本页条数(默认0)
regionstring–国家站点 ID/JP/MX/MY/PH/SG/TH/VN(默认 MY)

No output schema declared.

No examples provided.

tiktok_shop_hot_products ~213

获取TikTok商城热卖榜。按站点返回当前热卖商品,顺序即榜单顺序。返回商品ID、标题、主图、价格、销量、评分、店铺与链接。支持 ID/JP/MX/MY/PH/SG/TH/VN,US/GB/BR 不支持;翻页用 exclude_product_ids。单价¥0.2/次,空榜不计费。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
countnumber–返回条数 1~100(默认 20)
exclude_product_idsstring–翻页用:已拿到的商品ID,逗号分隔
regionstring–国家站点 ID/JP/MX/MY/PH/SG/TH/VN(默认 MY;US/GB/BR 不支持)

No output schema declared.

No examples provided.

tiktok_shop_product_detail ~157

获取TikTok商品详情。返回标题、售价/划线价、sold_count、评分、SKU 与库存、店铺、类目路径、主图、物流。 支持站点 ID/JP/MX/MY/PH/SG/TH/VN(US/GB/BR 不支持)。单价¥0.2/次,仅成功调用计费。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
product_idstringyes商品ID
regionstring–国家站点 ID/JP/MX/MY/PH/SG/TH/VN(默认 MY)

No output schema declared.

No examples provided.

tiktok_shop_product_reviews ~172

获取TikTok商品评论。返回 product_reviews[](评分、内容、图片、规格、国家)、review_ratings 分布、total_reviews、has_more。 支持站点 ID/JP/MX/MY/PH/SG/TH/VN(US/GB/BR 不支持)。单价¥0.2/次,仅成功调用计费。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
page_startnumber–页号(从1起,每页20条)
product_idstringyes商品ID
regionstring–国家站点 ID/JP/MX/MY/PH/SG/TH/VN(默认 MY)

No output schema declared.

No examples provided.

tiktok_shop_product_search ~193

搜索TikTok商城商品。返回 products[] 与 has_more;翻页把上一页 load_more_params 的 offset/page_token 原样回传。 支持站点 ID/JP/MX/MY/PH/SG/TH/VN(US/GB/BR 不支持)。单价¥0.2/次,仅成功调用计费。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
offsetnumber–起始位置,传上一页load_more_params.offset
page_tokenstring–翻页令牌,传上一页load_more_params.page_token
regionstring–国家站点 ID/JP/MX/MY/PH/SG/TH/VN(默认 MY)
search_wordstringyes搜索关键词

No output schema declared.

No examples provided.

tiktok_shop_seller_products ~177

获取TikTok店铺商品。返回 products[] 与 has_more;翻页把上一页 load_more_params.search_params 原样回传。 支持站点 ID/JP/MX/MY/PH/SG/TH/VN(US/GB/BR 不支持)。单价¥0.2/次,仅成功调用计费。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
regionstring–国家站点 ID/JP/MX/MY/PH/SG/TH/VN(默认 MY)
search_paramsstring–翻页令牌,传上一页load_more_params.search_params
seller_idstringyes店铺ID(seller_id)

No output schema declared.

No examples provided.

tiktok_sub_comments ~127

获取TikTok评论回复。返回二级评论的正文、点赞数、回复者信息与时间。追踪评论区的二次讨论与争议点时用,需先拿到主评论ID。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
comment_idstringyes评论ID
item_idstringyes视频ID

No output schema declared.

No examples provided.

tiktok_user_info ~122

获取TikTok用户信息。返回账号昵称、粉丝数、获赞数、简介与认证状态。做达人筛选、账号画像或粉丝量级分组时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
sec_uidstring–secUid
unique_idstring–用户名

No output schema declared.

No examples provided.

tiktok_user_posts ~122

获取TikTok用户视频列表。返回该账号发布的内容列表,按时间倒序,含每条内容ID与基础互动数据。监测账号更新频率、内容策略或批量取该账号内容ID时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
sec_uidstringyessecUid

No output schema declared.

No examples provided.

tw_keyword_search ~127

搜索推文。返回推文列表,含每条内容ID与基础互动数据。做关键词监测、内容发现或构建候选集时用,ID可继续调详情与评论接口。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
keywordstringyes关键词
search_typestring–类型(默认 Latest)

No output schema declared.

No examples provided.

tw_post_comments ~156

获取推文评论(回复)。返回评论正文、点赞数、回复数、评论者昵称与地区、时间戳,按页返回。做评论情感分析、竞品口碑对比或舆情监测时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。翻页深度受平台可见范围限制,超出后上游不再返回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
cursorstring–翻页游标
tweet_idstringyes推文ID

No output schema declared.

No examples provided.

tw_post_detail ~119

获取推文详情。返回正文、点赞/转推/回复/引用数、作者信息、媒体、发布时间。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
tweet_idstringyes推文ID

No output schema declared.

No examples provided.

tw_trending ~110

获取推特趋势话题。返回正文、点赞/转推/回复/引用数、作者信息、媒体、发布时间。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。

No output schema declared.

No examples provided.

tw_user_info ~121

获取推特用户信息。返回账号昵称、粉丝数、获赞数、简介与认证状态。做达人筛选、账号画像或粉丝量级分组时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
rest_idstring–rest_id
screen_namestring–@handle

No output schema declared.

No examples provided.

tw_user_posts ~151

获取用户推文列表(screen_name 与 rest_id 二选一)。返回该账号发布的内容列表,按时间倒序,含每条内容ID与基础互动数据。监测账号更新频率、内容策略或批量取该账号内容ID时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
cursorstring–翻页游标
rest_idstring–rest_id
screen_namestring–@handle

No output schema declared.

No examples provided.

wechat_mp_account_articles ~244

获取微信公众号历史发文列表(文章 tab,单页)。返回每篇文章的标题、摘要、链接、封面、发布时间、是否付费。username 支持 gh_… / gh_…@app / 自定义微信号。做公众号内容库同步、竞品更新监控时用。翻页传上一页的 next_offset。单价¥0.2/次,仅成功调用计费,失败自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
item_show_typestring–栏目:article(默认)/video/audio/image
offsetstring–翻页游标(base64),首页留空,传上一页 next_offset
page_sizestring–每页条数(微信当前忽略此参数)
rawstring–true=原始响应;false=精简结构(默认 false)
usernamestringyes公众号 username(gh_… / gh_…@app / 自定义微信号)

No output schema declared.

No examples provided.

wechat_mp_account_profile ~155

获取微信公众号资料页。返回昵称、gh_username、IP 属地、原创文章数、认证主体类型、关联视频号。签名与头像该链路取不到(恒 null 并列在 unavailable[])。做账号画像、投放前背调时用。单价¥0.2/次,仅成功调用计费,失败自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
rawstring–true=原始响应;false=精简结构(默认 false)
usernamestringyes公众号 username(三种形态均可)

No output schema declared.

No examples provided.

wechat_mp_article_comments ~202

获取微信公众号文章的一级评论(单页,buffer 游标翻页)。返回评论内容、点赞数、IP 属地、是否精选、回复数与回复列表。做评论舆情、用户反馈分析时用。建议先取文章详情的 comment_id 提速一倍。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
bufferstring–翻页游标,首页留空,传上一页响应的 buffer
comment_idstring–文章评论 id(性能捷径,取自文章详情 content.comment_id)
rawstring–true=原始响应;false=精简结构(默认 false)
urlstringyes文章链接

No output schema declared.

No examples provided.

wechat_mp_article_detail ~205

获取微信公众号文章详情(H5 版,推荐)。返回标题、作者、公众号昵称与 username、正文 HTML、封面图、发布时间、合集信息、评论 id。做文章内容分析、公众号监测、RAG 语料入库时用。响应较慢(6~18s),客户端超时请设 30s 以上。单价¥0.2/次,仅成功调用计费,失败自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
h5string–true=H5 版(默认,正文稳定);false=原生版(快、字段少)
rawstring–true=原始响应;false=精简结构(默认 false)
urlstringyes文章链接 https://mp.weixin.qq.com/s/…

No output schema declared.

No examples provided.

weibo_hot_search ~104

获取微博热搜榜。返回当前榜单条目,含排名、标题或关键词、热度值。做趋势信号、选题参考时用,适合定时轮询。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。

No output schema declared.

No examples provided.

weibo_keyword_search ~129

按关键词搜索微博。返回帖子列表,含每条内容ID与基础互动数据。做关键词监测、内容发现或构建候选集时用,ID可继续调详情与评论接口。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
pagenumber–页码(默认 1)
querystringyes关键词

No output schema declared.

No examples provided.

weibo_post_comments ~171

获取微博帖子评论列表。返回评论正文、点赞数、回复数、评论者昵称与地区、时间戳,按页返回。做评论情感分析、竞品口碑对比或舆情监测时用。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。翻页深度受平台可见范围限制,超出后上游不再返回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
countnumber–每页数量(默认 20)
max_idstring–翻页游标
post_idstringyes微博ID

No output schema declared.

No examples provided.

weibo_post_detail ~124

获取微博帖子详情(含互动量)。返回正文、转发/评论/点赞数、发布者信息、发布时间与配图。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
post_idstringyes微博ID

No output schema declared.

No examples provided.

weibo_sub_comments ~118

获取微博评论的回复列表。返回二级评论的正文、点赞数、回复者信息与时间。追踪评论区的二次讨论与争议点时用,需先拿到主评论ID。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
comment_idstringyes评论ID

No output schema declared.

No examples provided.

weibo_user_info ~110

获取微博用户信息。返回账号昵称、粉丝数、获赞数、简介与认证状态。做达人筛选、账号画像或粉丝量级分组时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
uidstringyes用户UID

No output schema declared.

No examples provided.

weibo_user_posts ~133

获取微博用户帖子列表。返回该账号发布的内容列表,按时间倒序,含每条内容ID与基础互动数据。监测账号更新频率、内容策略或批量取该账号内容ID时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
pagenumber–页码(默认 1)
uidstringyes用户UID

No output schema declared.

No examples provided.

xhs_note_comments ~174

获取小红书笔记的一级评论列表。返回评论正文、点赞数、回复数、评论者昵称与地区、时间戳,按页返回。做评论情感分析、竞品口碑对比或舆情监测时用。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。翻页深度受平台可见范围限制,超出后上游不再返回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
note_idstringyes笔记ID
sort_strategystring–排序策略
startnumber–翻页游标

No output schema declared.

No examples provided.

xhs_note_detail ~140

获取小红书笔记详细信息,包括标题、内容、图片、视频等。返回笔记标题正文、点赞/收藏/评论数、作者信息、图片列表、话题标签、发布时间。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
note_idstringyes笔记ID

No output schema declared.

No examples provided.

xhs_note_search ~178

通过关键词搜索小红书笔记,支持排序和筛选。返回笔记列表,含每条内容ID与基础互动数据。做关键词监测、内容发现或构建候选集时用,ID可继续调详情与评论接口。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
keywordstringyes搜索关键词
note_timestring–笔记时间
note_typestring–笔记类型
pagenumber–页码(默认 1)
sort_typestring–排序方式

No output schema declared.

No examples provided.

xhs_sub_comments ~149

获取某条评论下的二级评论列表。返回二级评论的正文、点赞数、回复者信息与时间。追踪评论区的二次讨论与争议点时用,需先拿到主评论ID。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
comment_idstringyes父评论ID
note_idstringyes笔记ID
startnumber–翻页游标

No output schema declared.

No examples provided.

xhs_user_info ~126

获取小红书用户信息,包括粉丝数、笔记数、获赞数等。返回账号昵称、粉丝数、获赞数、简介与认证状态。做达人筛选、账号画像或粉丝量级分组时用。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
user_idstringyes用户ID

No output schema declared.

No examples provided.

xhs_user_notes ~138

获取用户发布的笔记列表,支持翻页。返回该账号发布的内容列表,按时间倒序,含每条内容ID与基础互动数据。监测账号更新频率、内容策略或批量取该账号内容ID时用。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
cursorstring–翻页游标
useridstringyes用户ID

No output schema declared.

No examples provided.

yt_keyword_search ~125

搜索YouTube视频。返回视频列表,含每条内容ID与基础互动数据。做关键词监测、内容发现或构建候选集时用,ID可继续调详情与评论接口。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
keywordstringyes关键词
order_bystring–排序

No output schema declared.

No examples provided.

yt_post_comments ~149

获取YouTube视频评论(返回continuation_token翻页)。返回评论正文、点赞数、回复数、评论者昵称与地区、时间戳,按页返回。做评论情感分析、竞品口碑对比或舆情监测时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。翻页深度受平台可见范围限制,超出后上游不再返回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
video_idstringyes视频ID

No output schema declared.

No examples provided.

yt_post_detail ~119

获取YouTube视频详情。返回标题、观看/点赞/评论数、频道信息、时长、发布时间、描述。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
video_idstringyes视频ID

No output schema declared.

No examples provided.

yt_sub_comments ~120

YouTube评论翻页与回复。返回二级评论的正文、点赞数、回复者信息与时间。追踪评论区的二次讨论与争议点时用,需先拿到主评论ID。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
continuation_tokenstringyes翻页token

No output schema declared.

No examples provided.

yt_user_info ~112

获取YouTube频道信息。返回账号昵称、粉丝数、获赞数、简介与认证状态。做达人筛选、账号画像或粉丝量级分组时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
channel_idstringyes频道ID

No output schema declared.

No examples provided.

yt_user_posts ~122

获取YouTube频道视频列表。返回该账号发布的内容列表,按时间倒序,含每条内容ID与基础互动数据。监测账号更新频率、内容策略或批量取该账号内容ID时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
channel_idstringyes频道ID

No output schema declared.

No examples provided.

zhihu_hot_list ~106

获取知乎热榜。返回回答正文、赞同/评论/收藏数、作者信息、发布时间。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。

No output schema declared.

No examples provided.

zhihu_keyword_search ~140

按关键词搜索知乎文章。返回回答列表,含每条内容ID与基础互动数据。做关键词监测、内容发现或构建候选集时用,ID可继续调详情与评论接口。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
keywordstringyes关键词
limitnumber–数量(默认 20)
offsetnumber–偏移

No output schema declared.

No examples provided.

zhihu_post_comments ~167

获取知乎回答评论列表。返回评论正文、点赞数、回复数、评论者昵称与地区、时间戳,按页返回。做评论情感分析、竞品口碑对比或舆情监测时用。单价¥0.2/次,仅成功调用计费,失败或空结果自动退回。翻页深度受平台可见范围限制,超出后上游不再返回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
answer_idstringyes回答ID
limitnumber–数量(默认 20)
offsetnumber–偏移

No output schema declared.

No examples provided.

zhihu_post_detail ~117

获取知乎回答详情。返回回答正文、赞同/评论/收藏数、作者信息、发布时间。做单条内容的互动量分析、素材入库或作为批量任务起点时用。单价¥0.1/次,仅成功调用计费,失败或空结果自动退回。

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
answer_idstringyes回答ID

No output schema declared.

No examples provided.

Install

How do I install the Finewisdom 社媒与电商数据接口 MCP server?

Finewisdom 社媒与电商数据接口 is a hosted endpoint at https://finewisdom.top/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 · finewisdom.top

# add to Claude Code
claude mcp add --transport http yy05idiot-finewisdom 'https://finewisdom.top/mcp'
Common questions

What is the Finewisdom 社媒与电商数据接口 MCP server?

Finewisdom 社媒与电商数据接口 is an MCP server listed in the public MCP registry as io.github.yy05idiot/finewisdom. 统一 Token 调用 103 个社媒与电商数据接口,覆盖抖音、小红书、TikTok、Instagram、YouTube、X、淘宝、京东等 15 个平台。按次 ¥0.1–0.3,成功才计费。 This page covers its hosted endpoint (https://finewisdom.top/mcp).

Is the Finewisdom 社媒与电商数据接口 MCP server safe to use?

Finewisdom 社媒与电商数据接口 scores 69 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 Finewisdom 社媒与电商数据接口 MCP server expose?

Finewisdom 社媒与电商数据接口 exposes 103 tools: item_get_1688, item_get_company_1688, item_review_1688, item_search_1688, item_search_img_1688, and 98 more. Their descriptions and schemas cost roughly 14,973 tokens of context every time the server is loaded.

Does the Finewisdom 社媒与电商数据接口 MCP server require authentication?

No. We connected to Finewisdom 社媒与电商数据接口 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Finewisdom 社媒与电商数据接口 MCP server still maintained?

Finewisdom 社媒与电商数据接口 is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Finewisdom 社媒与电商数据接口 MCP server?

VerifyMCP ran 13 checks on Finewisdom 社媒与电商数据接口, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.