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.

CUQU (找搭子) MCP Server

REMOTE · AGENT.CUQU.NET · SCANNED SEP 29

Find and book offline group events in 10+ China cities, or publish your own event. By CUQU.

Available components

remote · agent.cuqu.net 66
66 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 Security71
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1620 tokens (~202/item across 8 items; 8 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 9 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the CUQU (找搭子) MCP Server server?

CUQU (找搭子) MCP Server is a hosted endpoint at https://agent.cuqu.net/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 · agent.cuqu.net

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

  • 29 Sept 26 +38
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 28 Sept 26 28

    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 29 Sept 2026 · Probed https://agent.cuqu.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cuqu.net CN=WE1,O=Google Trust Services,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 c2d9f5c0982ddfd01363f0c3a4ac0bc7
SANs: cuqu.net, agent.cuqu.net, *.agent.cuqu.net
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agent.cuqu.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
cuqu.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent.cuqu.net/mcp Verified 200
http (plaintext) http://agent.cuqu.net/mcp Inconclusive 405
MCP tools · 8 exposed · ~1,493 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
check_in ~145

活动签到。 用户到达活动现场后，通过此工具完成签到。支持手机号/用户ID/签到码三种方式。 Args: activity_id: 活动 ID phone: 手机号（用于签到，需与报名时一致） user_id: 用户 ID（已登录用户） code: 签到码（现场扫码获取，或主理人提供的签到口令） Returns: JSON 字符串，包含签到状态和签到时间

NameTypeReqDescription
activity_idstringyes–
codestring––
phonestring––
user_idstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

create_activity ~292

主理人在粗趣小程序上发布新活动。 当用户（主理人）想创建/发布一个活动时调用此工具。 Args: title: 活动标题，如"周六桌游聚会" activity_type: 活动类型，如"桌游聚会"、"户外徒步"、"剧本杀/密室"等 date: 活动日期，格式"2026-08-22" time: 活动时间段，如"14:00-18:00" location: 活动地点，如"南山区·科兴科学园" max_participants: 最大参与人数，数字字符串或整数均可，如 "15" 或 15 price: 人均费用（元），数字字符串或整数均可，如 "39" 或 39，免费填 "0" 或 0 description: 活动描述和注意事项 organizer: 主理人名称 Returns: JSON 字符串，包含活动 ID 和详情链接

NameTypeReqDescription
activity_typestringyes–
datestringyes–
descriptionstring––
locationstringyes–
max_participants–––
organizerstring––
price–––
timestringyes–
titlestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

create_payment ~140

生成活动报名的支付链接和二维码。 报名后通过此工具获取支付链接，用户扫码或点击链接完成微信支付。 Args: order_id: 订单号（优先使用，从 register_event 结果中获取） activity_id: 活动 ID（无订单号时配合手机号使用） phone: 手机号（配合活动 ID 查找订单） Returns: JSON 字符串，包含支付链接、二维码 URL、支付方式和有效期

NameTypeReqDescription
activity_idstring––
order_idstring––
phonestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_urllink ~215

为小程序页面生成 URL Link（微信外可打开的标准链接）。 用户想获得某个页面（通常是活动详情页）的可分享链接时调用。 生成的 https://wxaurl.cn/ 链接可在短信、邮件、网页、AI 应用等微信外场景打开， 点击后唤起微信小程序对应页面。 Args: activity_id: 活动 ID。提供时自动映射到活动详情页（path=pages/activity/detail, query=id=xxx）。 path: 小程序页面路径，如 "pages/index/index"。提供 activity_id 时忽略。 query: 页面参数（urlencode 后的字符串），如 "id=act_001"。提供 activity_id 时忽略。 Returns: JSON 字符串，包含 URL Link、页面路径和参数

NameTypeReqDescription
activity_idstring––
pathstring––
querystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_activity_card ~146

获取活动的"卡片"数据（C 端工具包核心）。 当用户想直接看到某活动的小程序卡片（标题 + 封面 + 时间地点 + 价格 + 报名链接） 时调用此工具。返回的卡片包含： - url_link: 小程序 URL Link（微信外点击唤起小程序活动页） - h5_url: H5 活动页地址（AI 应用内直接打开） Args: activity_id: 活动 ID Returns: JSON 字符串，包含活动卡片数据

NameTypeReqDescription
activity_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

query_activities ~218

查询粗趣小程序上的活动列表。 当用户想找活动、看有什么活动、按条件筛选活动时调用此工具。 Args: activity_type: 活动类型筛选，如"桌游聚会"、"户外徒步"、"剧本杀"、"飞盘"等。留空则不筛选。 date: 日期筛选，格式"2026-08-22"。留空则不筛选。 location: 区域筛选，如"南山区"、"罗湖区"。留空则不筛选。 keyword: 关键词搜索活动标题和描述。留空则不搜索。 Returns: JSON 字符串，包含活动列表（标题、时间、地点、价格、剩余名额、H5 链接等）

NameTypeReqDescription
activity_typestring––
datestring––
keywordstring––
locationstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

query_venues ~183

查询粗趣小程序合作场地列表。 当用户需要找场地、了解场地信息时调用此工具。 Args: venue_type: 场地类型，如"桌游吧"、"运动场地"、"露营基地"等。留空则不筛选。 location: 区域，如"南山区"、"罗湖区"。留空则不筛选。 min_capacity: 最少容纳人数，整数或数字字符串均可，如 10 或 "10"。填0则不筛选。 Returns: JSON 字符串，包含场地列表（名称、类型、位置、容量、价格区间、设施等）

NameTypeReqDescription
locationstring––
min_capacity–––
venue_typestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

register_event ~154

用户报名参加活动。 当用户确定要报名某个活动时调用此工具。报名后需要完成支付才能锁定名额。 Args: activity_id: 活动 ID（从 query_activities 结果中获取） user_name: 报名人姓名 phone: 手机号（用于接收活动通知和签到） note: 备注，如饮食禁忌、特殊需求等（可选） Returns: JSON 字符串，包含订单号、支付链接和支付二维码 URL

NameTypeReqDescription
activity_idstringyes–
notestring––
phonestringyes–
user_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the CUQU (找搭子) MCP Server server?

CUQU (找搭子) MCP Server is listed in the public MCP registry as io.github.cuqu-net/cuqu-mcp. Find and book offline group events in 10+ China cities, or publish your own event. By CUQU. This page covers its hosted endpoint (https://agent.cuqu.net/mcp).

Is the CUQU (找搭子) MCP Server server safe to use?

CUQU (找搭子) MCP Server scores 66 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 CUQU (找搭子) MCP Server server expose?

CUQU (找搭子) MCP Server exposes 8 tools: query_activities, create_activity, register_event, create_payment, check_in, and 3 more. Their descriptions and schemas cost roughly 1,493 tokens of context every time the server is loaded.

Does the CUQU (找搭子) MCP Server server require authentication?

Yes. CUQU (找搭子) MCP Server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the CUQU (找搭子) MCP Server server still maintained?

CUQU (找搭子) MCP Server is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.