CUQU找搭子 (CUQU) MCP Server

Most tools target distinct actions (query_activities, query_venues, create_activity, check_in), but two pairs overlap: register_event already returns a payment link/QR while create_payment exists separately to generate one, and get_activity_card returns a url_link that generate_urllink also produces. An agent could reasonably pick the wrong one of these pairs, though descriptions give hints.

All names are snake_case and mostly follow verb_noun (create_activity, query_venues, get_activity_card, generate_urllink, register_event). Minor deviations: check_in is verb-only with no object, and the verb set mixes query/get/create/register/check.

Eight tools is well within a comfortable range for an activity-booking domain. Each maps to a distinct step in the lifecycle: browse, publish, register, pay, check in, share, and venue lookup.

The surface covers create/browse/register/pay/check-in but has no update_activity, no cancel registration or refund path, and no order/registration lookup, so several real workflows dead-end. get_activity (single detail) is also only approximated by get_activity_card.