No user-submitted related servers found.
Scored across 130 tools
The server has many product-specific tools with clear prefixes (vod, live, vads, caas, ai, edge, storage), but generic invoke_*_api tools overlap heavily with the named tools, and similarly named operations exist across products (e.g., list_buckets vs list_ai_buckets vs list_storage_api_buckets, multiple get_domain variants). Descriptions give exact endpoints, but an agent could still misselect when product context is absent.
Nearly all tools use snake_case verb_noun, but consistency is only mostly maintained: some tools carry product prefixes (list_vod_videos), some do not (list_domains, list_servers), and version suffixes appear (list_servers_v3 vs list_servers). The generic invoke_*_api tools follow a predictable pattern, and S3 head_* verbs are conventional. These are minor deviations rather than chaotic naming.
130 tools is far beyond typical scoped MCP server size, and many named tools are made redundant by generic invoke_*_api tools that already cover large API surfaces. While the server spans many products, the count is overwhelming and likely to burden tool selection and agent reliability.
The surface is extremely broad across CDN, DNS, VOD, Live, VADS, IaaS, CaaS, AI, Edge, and Storage, with CRUD for many resources and generic API invokers to fill undocumented or missing operations. However, some named product areas lack full lifecycle operations (e.g., VOD channels/videos) and rely on generic invokers, so coverage is strong but not seamless.
