Remote MCP · Endpoint

24好玩 · 互动营销模板与案例库 MCP server

No. 24好玩 · 互动营销模板与案例库 answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://mcp.24haowan.com/mcp

The last check completed an MCP handshake.

Registry name
com.24haowan/marketing
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
768 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
检索 24好玩 H5 互动营销平台的活动模板库、客户案例库与帮助知识库。匿名只读,无需 API Key。
Listing
From the official MCP registry (active).
Recent checks of 24好玩 · 互动营销模板与案例库
CheckedResultHandshake
6 hours agoHandshake completed768 ms
2 days agoHandshake completed929 ms
4 days agoHandshake completed791 ms
5 days agoHandshake completed785 ms
7 days agoHandshake completed768 ms
8 days agoHandshake completed818 ms
9 days agoHandshake completed910 ms
12 days agoHandshake completed799 ms
13 days agoHandshake completed832 ms
15 days agoHandshake completed1.11 s
16 days agoHandshake completed824 ms
17 days agoHandshake completed843 ms
18 days agoHandshake completed909 ms
19 days agoHandshake completed835 ms
20 days agoHandshake completed870 ms
21 days agoHandshake completed818 ms
22 days agoHandshake completed815 ms

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

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 24好玩 · 互动营销模板与案例库 and makes no claim about it beyond what these checks measured.