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 · SCANNED OCT 1

统一 Token 调用 89 个社媒与电商数据接口,覆盖抖音、小红书、微博、B站、视频号、TikTok 与淘宝、京东、1688 等 14 平台,注册赠 20 次。

Available components

58 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2234 tokens (~74/item across 30 items; 30 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage58
  • 37% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
  • 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 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 31 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
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "yy05idiot-finewisdom": {
      "url": "https://finewisdom.top/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "yy05idiot-finewisdom": {
      "type": "http",
      "url": "https://finewisdom.top/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.yy05idiot-finewisdom]
url = "https://finewisdom.top/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yy05idiot-finewisdom": {
      "type": "remote",
      "url": "https://finewisdom.top/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yy05idiot-finewisdom --url 'https://finewisdom.top/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  yy05idiot-finewisdom:
    url: "https://finewisdom.top/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "yy05idiot-finewisdom": {
      "Transport": "http",
      "Url": "https://finewisdom.top/mcp"
    }
  }
}
# add to Vellum
assistant mcp add yy05idiot-finewisdom -t streamable-http -u 'https://finewisdom.top/mcp'
// mcp.json
{
  "mcpServers": {
    "yy05idiot-finewisdom": {
      "type": "http",
      "url": "https://finewisdom.top/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 1 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 30 Sept 26 58

    First indexed and scored.

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 1 Oct 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 24 Aug 2026 22 Nov 2026 RSA 2048 SHA256-RSA 5da63df54808db65536a44652bc9fa6cbd8
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. present 26780, 41508 8, 13 Verified
finewisdom.top. absent 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 · 30 exposed · ~2,129 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
bili_video ~57

B站视频详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
bv_idstringyesBV号

No output schema declared.

No examples provided.

channels_comments ~98

视频号作品评论列表(object_id 从作品详情返回的 id 字段获取)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
comment_idstring–评论ID(取回复用)
last_bufferstring–翻页游标
object_idstringyes作品ID

No output schema declared.

No examples provided.

channels_video ~87

视频号作品详情(传分享链接 share_url,形如 https://weixin.qq.com/sph/xxxx)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
object_idstring–作品ID
share_urlstring–分享链接

No output schema declared.

No examples provided.

company_1688 ~64

1688商家/公司详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
seller_idstringyes商家ID

No output schema declared.

No examples provided.

douyin_author ~71

抖音作者主页信息(粉丝/获赞/作品数)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
sec_user_idstringyes作者sec_uid

No output schema declared.

No examples provided.

douyin_product ~59

抖音商品详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
product_idstringyes商品ID

No output schema declared.

No examples provided.

douyin_search ~72

抖音关键词搜索视频

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
keywordstringyes关键词
pagenumber–页码(默认 0)

No output schema declared.

No examples provided.

douyin_video ~77

抖音视频详情:标题/点赞/评论/分享数、作者信息、封面音乐等

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
aweme_idstringyes视频ID

No output schema declared.

No examples provided.

douyin_video_comments ~75

抖音视频评论列表

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
aweme_idstringyes视频ID
pagenumber–页码(默认 0)

No output schema declared.

No examples provided.

ecommerce_comments ~69

淘宝/京东商品评论列表(platform=淘宝 或 京东)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
idstringyes目标对象ID

No output schema declared.

No examples provided.

ecommerce_item ~68

淘宝/京东商品详情(platform=淘宝 或 京东)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
idstringyes目标对象ID

No output schema declared.

No examples provided.

ecommerce_shop ~78

京东/淘宝店铺在售商品搜索(京东传 shop_id;淘宝传 seller_id+shop_id)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
idstringyes目标对象ID

No output schema declared.

No examples provided.

ig_post ~58

Instagram帖子详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
codestringyes帖子shortcode

No output schema declared.

No examples provided.

img_search_1688 ~68

1688以图搜图(传商品图片URL)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
image_urlstringyes图片URL

No output schema declared.

No examples provided.

item_1688 ~60

1688商品详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
item_idstringyes商品ID

No output schema declared.

No examples provided.

ks_video ~57

快手视频详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
photo_idstringyes视频ID

No output schema declared.

No examples provided.

reviews_1688 ~93

1688商品评论(需 item_id + seller_nick)

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
item_idstringyes商品ID
pagenumber–页码(默认 1)
seller_nickstringyes商家昵称

No output schema declared.

No examples provided.

search_1688 ~73

1688关键词搜索商品

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

No output schema declared.

No examples provided.

tiktok_search ~57

TikTok关键词搜索

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
keywordstringyes关键词

No output schema declared.

No examples provided.

tiktok_video ~58

TikTok视频详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
item_idstringyes视频ID

No output schema declared.

No examples provided.

tw_post ~59

Twitter/X推文详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
tweet_idstringyes推文ID

No output schema declared.

No examples provided.

weibo_comments ~87

微博帖子评论列表

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 ~59

微博帖子详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
post_idstringyes微博ID

No output schema declared.

No examples provided.

xhs_note ~63

小红书笔记详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
note_idstringyes笔记ID

No output schema declared.

No examples provided.

xhs_note_comments ~88

小红书笔记评论列表

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
note_idstringyes笔记ID
sort_strategystring–排序策略
startstring–翻页游标

No output schema declared.

No examples provided.

xhs_note_search ~112

小红书笔记关键词搜索

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_user ~59

小红书用户信息

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
user_idstringyes用户ID

No output schema declared.

No examples provided.

yt_video ~57

YouTube视频详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
video_idstringyes视频ID

No output schema declared.

No examples provided.

zhihu_comments ~84

知乎回答评论列表

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

No output schema declared.

No examples provided.

zhihu_post ~62

知乎回答/帖子详情

NameTypeReqDescription
_tokenstring–备用鉴权:fw_ 开头的 token(推荐改用 HTTP Header X-FW-Token,二选一)
answer_idstringyes回答ID

No output schema declared.

No examples provided.

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 调用 89 个社媒与电商数据接口,覆盖抖音、小红书、微博、B站、视频号、TikTok 与淘宝、京东、1688 等 14 平台,注册赠 20 次。 This page covers its hosted endpoint (https://finewisdom.top/mcp).

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

Finewisdom 社媒与电商数据接口 scores 58 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 30 tools: douyin_video, douyin_search, douyin_video_comments, douyin_author, douyin_product, and 25 more. Their descriptions and schemas cost roughly 2,129 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 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.