Remote MCP · Endpoint

Finewisdom 社媒与电商数据接口 MCP server

No. Finewisdom 社媒与电商数据接口 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://finewisdom.top/mcp

The last check completed an MCP handshake.

Registry name
io.github.yy05idiot/finewisdom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
772 ms
Tools exposed
30 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
统一 Token 调用 89 个社媒与电商数据接口,覆盖抖音、小红书、微博、B站、视频号、TikTok 与淘宝、京东、1688 等 14 平台,注册赠 20 次。
Listing
From the official MCP registry (active).
Recent checks of Finewisdom 社媒与电商数据接口
CheckedResultHandshake
1 hour agoHandshake completed772 ms
2 days agoHandshake completed762 ms
4 days agoHandshake completed736 ms
6 days agoHandshake completed859 ms
8 days agoHandshake completed848 ms
10 days agoHandshake completed679 ms
13 days agoHandshake completed680 ms
14 days agoHandshake completed695 ms
16 days agoHandshake completed1.98 s
17 days agoHandshake completed667 ms
18 days agoHandshake completed864 ms
21 days agoHandshake completed654 ms
22 days agoHandshake completed1.77 s
24 days agoHandshake completed1.33 s

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Finewisdom 社媒与电商数据接口 and makes no claim about it beyond what these checks measured.