BlazingCDN-MCP
OfficialRelated Servers
Alternatives to BlazingCDN-MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceOfficial MCP Server for GPT-5.6 Sol Coding & Reasoning API. Connects extended reasoning capabilities directly into Claude Desktop, Cursor, and Windsurf.-
- AlicenseNot gradedqualityDmaintenancePublic MCP server for integrating Cuprice pricing widgets from AI tools like Cursor, Claude Desktop, and Claude Code.1MIT
- AlicenseBqualityDmaintenanceThe official MCP server for Semantic Pen - an advanced AI article generator and SEO content writer. Create, manage, and optimize SEO-friendly articles directly from Claude Code and Cursor Windsurf with powerful AI automation.511 npm2MIT
- AlicenseAqualityAmaintenanceOfficial MCP Server for Human Search Intent Keywords, Google Lighthouse Core Web Vitals (CLS/LCP/INP), Technical SEO Audits, and On-Page Diagnostic Intelligence.530 npm1MIT
- AlicenseAqualityDmaintenanceOfficial MCP server for FormaCV, enabling AI-powered CV formatting, anonymization, tailoring, and ATS push-back from AI agents like Claude Desktop and Cursor.824 npm1MIT
- AlicenseBqualityCmaintenanceOfficial MCP server for ZapifyAPI, providing AI agents access to 32 tools across image conversion, text analysis, network diagnostics, developer utilities, and data conversion.3211 npmMIT
TDQS
Scored across 29 tools
Most tools target a distinct resource type or action, such as listing vs getting vs searching. The only real ambiguities are list_custom_domains versus search_custom_domains and get_vcdn_files_total versus list_vcdn_files, but their descriptions sufficiently clarify the difference.
The dominant pattern is verb_noun with snake_case, using list_ and get_ consistently for most resources. Minor deviations like list_ftp_logins and list_auto_imports omitting the vcdn_ prefix, and using 'statistics' instead of 'metrics', keep it from being perfectly consistent.
29 tools is above the ideal 3-15 range and feels heavy, but the server covers multiple product families: Anycast CDN, Video CDN, Cloud Storage, external storage, docs, and pricing. Several settings getters could likely be consolidated, so the count is borderline rather than clearly excessive.
The toolset is strong for read-only inspection, metrics, cache operations, and cost estimation, but it lacks create/update/delete tools for resources, buckets, domains, external storages, and settings. Agents can diagnose and purge/warm caches but cannot perform full CDN configuration changes, which is a significant lifecycle gap.