No user-submitted related servers found.
Scored across 877 tools
While service prefixes help separate many tools, the sheer 877-tool surface contains multiple near-duplicate and overlapping variants: ncloud_get_price_list vs ncloud_get_product_price_list, delete_rule_group vs delete_rule_group_by_id, delete_metrics_group variants, and sourcecommit by_id duplicates. These overlapping boundaries will cause frequent misselection even with strong descriptions.
The dominant ncloud_<service>_<verb>_<noun> pattern is readable and consistent across most services, but there are notable deviations: lb vs load_balancer, ncloud_list_pipelines vs ncloud_pipeline_list_*, and mixed update/edit/change/set/put verbs. It is not chaotic, but it is not uniform enough for a 4.
877 tools is an extreme mismatch for a single MCP server, far beyond even the heaviest reasonable scope. A server this large should be split into per-service or per-domain MCP servers to remain navigable and effective.
The server provides surprisingly deep lifecycle coverage across compute, network, storage, databases, Kubernetes, KMS, certificate management, CI/CD, monitoring, billing, and object storage. Minor gaps exist—such as missing DRM site deletion, no CDN+/GlobalCDN instance lifecycle operations, and no branch/tag write operations for SourceCommit—but these are not widespread dead ends.