Skip to main content
Glama
hostkey-cloud-ru

hostkey-mcp-server-ru

Official
by hostkey-cloud-ru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hostkey-mcp-server-ru

No user-submitted related servers found.

    Related Servers

    • Hetzner MCP

      Xodus-CO
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to manage Hetzner Cloud resources including servers, load balancers, and volumes through natural language commands. It facilitates infrastructure operations such as resource creation, security configuration, and real-time pricing queries within AI-powered environments.
      85 npm
      1
      -

    • webdock-mcp-server

      heaventree
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI clients to manage Webdock.io VPS infrastructure through natural language, including provisioning servers, handling snapshots, managing SSH/shell users and scripts, configuring webhooks, and inspecting account or billing details.
      MIT

    • lunanode-mcp

      Burntberry
      A
      license
      A
      quality
      B
      maintenance
      Enables management of LunaNode VPS resources including VMs, images, volumes, floating IPs, SSH keys through natural language with tiered safety controls.
      12
      MIT
    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

    B3.2/5.0

    Scored across 132 tools

    Disambiguation3/5

    Most tools have distinct verb_noun names and clear descriptions, but with 132 tools there are several closely related pairs (e.g., get_servers vs get_server, s3_get_buckets vs s3_get_buckets_via_queue, create_reinstall_task vs reinstall_server) that could cause misselection. The catch-all call_api_raw also overlaps with many typed tools, increasing ambiguity.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (get_, list_, create_, delete_, etc.) with domain prefixes like s3_, request_rh_, and pdns_. While there are minor deviations (e.g., port_on vs set_main_ip, or occasional camelCase like add_iso_image), the overall schema is predictable and readable.

    Tool Count1/5

    132 tools is an extreme count, far exceeding the 50+ threshold considered appropriate. Even for a comprehensive cloud provider API, this volume overwhelms an agent's tool-selection capability and significantly increases the chance of misselection. The server would benefit from consolidation or hierarchical grouping.

    Completeness4/5

    The tool surface covers CRUD and lifecycle operations across multiple domains: servers, network, DNS, S3, billing, and remote hands. Obvious gaps are rare (e.g., no direct server rename or tag edit tool, but these are edge cases). The presence of a raw API call tool also fills potential holes, so agents can accomplish most tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources