Skip to main content
Glama
Sign In
sniper35

Verda Cloud MCP Server

by sniper35
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Verda Cloud MCP Server

No user-submitted related servers found.

    Related Servers

    • nometria by nometria

      nometriaofficial

      nometria
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables deploying and managing projects across AWS, Google Cloud, Azure, DigitalOcean, Hetzner, and Vercel directly from Claude Code, with tools for instance lifecycle, domains, environment variables, backend services, databases, webhooks, and GitHub integration.
      96 npm
      3
      MIT

    • Vast.ai MCP Server

      CryDevOk
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables comprehensive management of Vast.ai GPU cloud instances, including searching for GPU offers, creating and managing instances, executing remote commands via SSH, and monitoring background tasks for ML training workflows.
      13
      MIT
    • @vertracloud/mcp by vertracloud

      @vertracloud/mcpofficial

      vertracloud
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to operate Vertra Cloud resources through the public API: deploy and manage applications, view logs and metrics, create and restore snapshots, and administer databases and environment variables.
      138
      476 npm
      2
      MIT

    • CloudGPU MCP

      mrhy7176
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to check live GPU prices, get a cost quote, rent a per-minute GPU instance, upload code and data, run jobs in the background, tail logs, download results and destroy the instance to stop billing. Includes guardrail limits on spend, hours and idle time, safe file transfer, and access to an OpenAI-compatible model API for inference without renting a GPU.
      606 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs (instances, volumes, scripts, SSH keys, config). The main ambiguity is between check_spot_availability, monitor_spot_availability, and deploy_spot_instance—especially since monitor can auto-deploy, blurring its boundary with deploy_spot_instance. create_startup_script and create_and_set_default_script also overlap slightly.

    Naming Consistency5/5

    Tool names consistently follow verb_noun snake_case, e.g., list_instances, create_volume, attach_volume, delete_instance. Minor compounds like create_and_set_default_script and show_config vs list_* are acceptable deviations and don't create confusion.

    Tool Count3/5

    With 20 tools, the server is on the heavier side for a cloud management MCP. While most tools have a purpose, some areas (script management, volume management, spot monitoring) could be consolidated without losing clarity, making the count feel slightly bloated.

    Completeness3/5

    Core instance lifecycle is covered (deploy, list, check, start, shutdown, delete), but there are notable gaps: volumes can be created/listed/attached/detached but not deleted; scripts can be created and set as default but not edited or deleted; SSH keys can be listed but not added or removed. There is also no on-demand instance creation separate from spot deployment.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources