Skip to main content
Glama
ParalonCloud

paraloncloud-rentals

Official
by ParalonCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to paraloncloud-rentals

No user-submitted related servers found.

    Related Servers

    • vastai-mcp

      dam2452
      F
      license
      A
      quality
      D
      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
      -
    • Latitude.sh MCP Server by latitudesh

      Latitude.sh MCP Serverofficial

      latitudesh
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language management of Latitude.sh infrastructure, allowing users to list, create, and delete servers, projects, and SSH keys through MCP-compatible clients.
      33 npm
      4
      MIT

    • gpusmarket

      jyswee
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for renting real GPUs from the terminal. Enables browsing, renting, chatting, managing, and pooling GPU instances with per-second billing, designed for AI agents.
      46 npm
      1
      -
    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.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Provider and renter operations are clearly separated, and each tool names a distinct resource+action. There is some overlap: update_node can also change 'available' and 'price_per_hour', which collides with set_node_available and set_node_price, and reclaim_spot_node overlaps with set_node_available(false) on spot nodes. The descriptions clarify the difference (batch vs. single-field, spot-specific semantics), so misselection is unlikely but not impossible.

    Naming Consistency5/5

    All 17 tools follow a consistent verb_noun snake_case pattern (list_my_nodes, set_node_access, create_rental, destroy_rental). The role prefixes (my/rental/node) are used predictably, and read vs. write is obvious from the verb. Minor variation between add_node and create_rental is the only deviation and does not break the pattern.

    Tool Count4/5

    17 tools is on the heavy side of the sweet spot but justified because the server serves two distinct roles (provider node management and renter GPU usage). Almost every tool maps to a real operation earning its place. It could be tightened if update_node absorbed the single-field setters.

    Completeness4/5

    The renter lifecycle (list_gpus, create_rental, get_rental, destroy_rental, list_rentals) and provider lifecycle (add, install command, get/list, price, availability, access, earnings) are well covered. Notable gaps: there is no way to remove/delete a node from the account once added, and no credit top-up or payout operation (payouts explicitly excluded). These are minor and documented, so agents can mostly work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources