Skip to main content
Glama
KaranKataria77

vastai-mcp

by KaranKataria77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vastai-mcp

No user-submitted related servers found.

    Related Servers

    • vastai-mcp

      dam2452
      F
      license
      A
      quality
      B
      maintenance
      MCP server that wraps the Vast.ai REST API to enable LLM agents to search GPU marketplace, rent machines, manage instance lifecycle, run commands, and inspect billing.
      20
      1
      -

    • 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.
      12
      MIT

    • vastai-host-mcp

      Cogni-AI-OU
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Vast.ai providers to manage hosted machines, update pricing, run self-tests, and automate host operations through natural language.
      MIT
    • meshive-mcp by meshive

      meshive-mcpofficial

      meshive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: GPU pricing snapshots, rentable offers, volume creation, volume listing, instance creation, and billing. list_gpus and search_offers are related but clearly differ in granularity, and the descriptions prevent confusion.

    Naming Consistency4/5

    Most tool names follow a clear verb_noun pattern such as list_gpus, create_volume, and create_instance. billing_summary is the only real outlier, being a noun phrase rather than a verb-led action, but the overall convention remains predictable.

    Tool Count5/5

    Six tools is well within the ideal scope for a focused rental-management server. Each tool serves a necessary step in the core workflow, and there is no obvious bloat or redundancy.

    Completeness2/5

    The tool set covers discovery, creation, volume listing, and billing, but it lacks essential lifecycle operations such as listing instances, terminating instances, and deleting volumes. This creates significant dead ends: resources can be created but not managed or cleaned up.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources