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.

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

REMOTE · MCP.24HAOWAN.COM · 2 COMPONENTS · SCANNED SEP 21

检索 24好玩 H5 互动营销平台的活动模板库、客户案例库与帮助知识库。匿名只读,无需 API Key。

+3 this week 89 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 Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • 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 1534 tokens (~170/item across 9 items; 8 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
  • Supports UI / widget rendering.Pass
Install

How do I install the 24好玩 · 互动营销模板与案例库 MCP server?

24好玩 · 互动营销模板与案例库 is a hosted endpoint at https://mcp.24haowan.com/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.24haowan.com

# add to Claude Code
claude mcp add --transport http com-24haowan-marketing 'https://mcp.24haowan.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-24haowan-marketing": {
      "url": "https://mcp.24haowan.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-24haowan-marketing": {
      "type": "http",
      "url": "https://mcp.24haowan.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-24haowan-marketing]
url = "https://mcp.24haowan.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-24haowan-marketing": {
      "type": "remote",
      "url": "https://mcp.24haowan.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-24haowan-marketing --url 'https://mcp.24haowan.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-24haowan-marketing:
    url: "https://mcp.24haowan.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-24haowan-marketing": {
      "Transport": "http",
      "Url": "https://mcp.24haowan.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-24haowan-marketing -t streamable-http -u 'https://mcp.24haowan.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-24haowan-marketing": {
      "type": "http",
      "url": "https://mcp.24haowan.com/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.

  • 21 Sept 26 +1
    • Stability: 0.97 → pass security
  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 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.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

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 Sept 2026 · Probed https://mcp.24haowan.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.24haowan.com CN=YR2,O=Let's Encrypt,C=US 22 Aug 2026 20 Nov 2026 RSA 2048 SHA256-RSA 595cc805bf5f92c27f213a17f460f8deebd
SANs: *.24haowan.com, 24haowan.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 mcp.24haowan.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
24haowan.com. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.24haowan.com/mcp Verified 200
http (plaintext) http://mcp.24haowan.com/mcp HTTPS enforced 308 https://mcp.24haowan.com/mcp
MCP tools · 8 exposed · ~1,062 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
get_case ~57

按 slug 获取单个客户案例的完整正文(背景、做法、效果口径)。slug 来自 list_cases 的返回。

NameTypeReqDescription
slugstringyes案例 slug,例如 csair、k11、powerlong

No output schema declared.

No examples provided.

get_industry_benchmark ~175

返回该行业在 24好玩平台上真实活动的基准:总中奖率、奖池档位数、活动周期、参与量级、实际中奖率与核销率,全部为按商户等权的中位数并附样本量。用于回答「中奖率设多少」「奖池分几档」「活动开几天」这类要有出处的数字问题。★ 平台没有奖品单价/预算/ROI 数据,本工具**不返回任何金额**,也不要据此推算预算。

NameTypeReqDescription
industrystring行业 slug,取值与 list_cases 的 industry 相同(用 list_industries 可取全部)。不传或该行业样本不足时,返回平台整体口径并明确说明。

No output schema declared.

No examples provided.

get_player_behavior ~140

返回 24好玩平台上玩家的真实行为分布:参与量在活动上线后怎么衰减、一天里什么时段来、助力类玩法一个人能拉到几个、各类玩法的人均次数与浏览转化率、玩家账号规模与画像可得性。用于回答「活动开几天有用」「什么时候推」「助力能不能拉新」「哪类玩法更黏」这类要有出处的问题。★ 平台级口径,**没有行业维度**;要按行业切的奖池/中奖率数字请用 get_industry_benchmark。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_template ~59

按模板 id 获取单个活动模板的完整信息:玩法类别、标签、适用行业、玩法介绍与详情页地址。模板 id 来自 search_templates 的返回。

NameTypeReqDescription
idstringyes模板 id,例如 336

No output schema declared.

No examples provided.

list_cases ~172

列出 24好玩的客户案例(真实交付案例与售前方案),可按行业、类型、关键词筛选。适合回答「你们做过 XX 行业的什么案例」。怎么用案例做参考、以及研究案例时的常见陷阱,见开放技能包全文:https://www.24haowan.com/open-skills/case-library

NameTypeReqDescription
industrystring行业 slug,用 list_industries 可取全部取值,例如 commercial-property
limitinteger返回条数,默认 20
querystring关键词,例如「商场开业」「银行」「扫码」
typestringdelivered=真实交付案例,proposal=售前方案。留空则两者都返回

No output schema declared.

No examples provided.

list_industries ~81

列出案例库的行业分类(slug + 名称 + 该行业导语与常见问题)。用于给 list_cases 的 industry 参数取值,也可直接回答「你们在 XX 行业做过什么」。

NameTypeReqDescription
with_faqboolean是否附带每个行业的常见问题,默认 false

No output schema declared.

No examples provided.

search_knowledge ~144

在 24好玩帮助中心全文里检索使用方法与常见问题:创建活动、编辑器配置、奖品与核销、账户充值、公众号授权、开放接口对接等。适合回答「怎么做 XX」「XX 怎么配置」。这里返回的是平台操作方法;奖池概率/预算/防刷的**设计**方法见开放技能包全文:https://www.24haowan.com/open-skills/prize-and-budget

NameTypeReqDescription
limitinteger返回文档条数,默认 3
querystringyes要查的问题或关键词,例如「怎么设置中奖概率」「奖品核销」

No output schema declared.

No examples provided.

search_templates ~234

在 24好玩活动市场里搜索可直接使用的 H5 互动营销模板(抽奖/转盘/刮刮乐/签到/答题/小游戏等)。可按关键词、玩法类别、行业筛选。适合回答「有没有适合 XX 场景的活动玩法」这类问题。选型判断(按行业/目标怎么选、活动怎么排结构)见开放技能包全文:https://www.24haowan.com/open-skills/campaign-planning

NameTypeReqDescription
categorystring玩法类别:lottery=抽奖类 score=分数类 signin=签到类 collect=集字类 test=测试类 create=生成类 help=助力类 complete=通关类
industrystring行业关键词,例如「商超」「餐饮」「地产」
limitinteger返回条数,默认 10
querystring关键词,可以是玩法、场景或节日,例如「转盘」「中秋」「商场开业」。留空则返回热门模板

No output schema declared.

No examples provided.

Common questions

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

24好玩 · 互动营销模板与案例库 is an MCP server listed in the public MCP registry as com.24haowan/marketing. 检索 24好玩 H5 互动营销平台的活动模板库、客户案例库与帮助知识库。匿名只读,无需 API Key。 This page covers its hosted endpoint (https://mcp.24haowan.com/mcp).

Is the 24好玩 · 互动营销模板与案例库 MCP server safe to use?

24好玩 · 互动营销模板与案例库 scores 89 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 24好玩 · 互动营销模板与案例库 MCP server expose?

24好玩 · 互动营销模板与案例库 exposes 8 tools: search_templates, get_template, list_cases, get_case, search_knowledge, and 3 more. Their descriptions and schemas cost roughly 1,062 tokens of context every time the server is loaded.

Does the 24好玩 · 互动营销模板与案例库 MCP server require authentication?

No. We connected to 24好玩 · 互动营销模板与案例库 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 24好玩 · 互动营销模板与案例库 MCP server still maintained?

24好玩 · 互动营销模板与案例库 is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.