MCP server providing tools for infrastructure management, VPS deployment, instance control, and computational operations via the CubePath SDK
Critical gaps across all dimensions. Tool definitions exist but lack essential schema documentation, parameter descriptions, and output specifications. No visible input schemas in provided source code, cannot verify Zod schema implementations. Descriptions are present but generic (10-50 chars, well below 194-char baseline). No error handling guidance, no parameter constraints, no output documentation. Destructive tools (destroyInstance, deployVps) lack confirmation patterns. Tool composition is reasonable (single responsibility), but interface quality is poor for LLM reasoning.
Performs mathematical calculations using mathjs
Deploys a new VPS instance with specified configuration
Permanently destroys a VPS instance
Displays formatted output or information
Retrieves the current status of a specific VPS instance
Lists available baremetal server models
Lists available CDN service plans
Lists all VPS instances owned by the user
No input schemas visible in source code. Cannot verify Zod schema implementations for any tool.
Descriptions are generic and under 50 characters (e.g., 'Displays formatted output or information', 'Performs mathematical calculations using mathjs'). Baseline is 194 chars. No guidance on WHEN to use each tool, WHAT it returns, or dependencies.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
Lists available load balancer service plans
Lists available deployment locations
Lists all projects associated with the user account
Lists all SSH keys associated with the user account
Lists available deployment templates
Lists available VPS pricing plans
Performs power operations (start, stop, reboot) on a VPS instance
Destructive tools (destroyInstance, deployVps) lack confirmation or dry-run patterns. No error guidance for recovery. Agents make mistakes, a confirm_before_execute pattern prevents catastrophic errors.'
No parameter descriptions visible. Rubric requires: 'Every parameter needs a description explaining what it controls.' Without descriptions, LLMs cannot infer valid values, ranges, or dependencies. Example: deployVps likely has parameters like 'location', 'plan', 'template', none documented.
No output schemas documented. Rubric: 'Document the output schema. LLMs need to know what fields to expect so they can plan downstream tool calls.' List tools (listInstances, listProjects, etc.) should document pagination, field names, and total count, none visible.