mcp_ruvds.com
Related Servers
Alternatives to mcp_ruvds.com
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceMCP server for the Hetzner Cloud API. Manage servers, networks, volumes, firewalls, load balancers, and more through the Model Context Protocol.185556 npm6Functional Source , Version 1.1, MIT Future
- AlicenseNot gradedqualityCmaintenanceOpen-source MCP server for managing Hetzner Cloud infrastructure with two management layers: * Layer 1 — Hetzner Cloud API (35 tools): Server power control, metrics, snapshots, backups, firewalls, DNS zones and records, rescue mode, server rebuild and rescale. Works even when the server OS is unresponsive. * Layer 2 — SSH (25 tools): Service management (systemd), Nginx config and reload,MIT
- AlicenseBqualityCmaintenanceManage VPS, domains, DNS, billing, and execute SSH commands from any MCP-compatible client. 27 tools + full API discovery across 500+ OVH endpoints.273MIT
- FlicenseAqualityDmaintenanceMCP server for YouGPU REST API that enables GPU catalog browsing, instance lifecycle management (create, stop, start, delete), and balance checking.11-
- FlicenseAqualityBmaintenanceEnables Claude, Cursor, and other MCP clients to manage Iotamine cloud VPS accounts via the Iotamine REST API, including VPS lifecycle, monitoring, billing, and support operations.78-
- AlicenseNot gradedqualityDmaintenanceMCP server for Hetzner. Enables managing cloud projects, account resources, and dedicated servers, with the entire REST API reachable through a searchable tool catalog.1MIT
TDQS
Scored across 26 tools
Many tools lack descriptions (e.g., ruvds_get_action, ruvds_server_action, ruvds_change_server), making it hard to distinguish their purposes. Names like ruvds_server_action, ruvds_server_cost, and ruvds_get_server overlap in scope without clear differentiation.
All tools share the 'ruvds_' prefix, but the naming pattern varies: some use verb_noun (list_servers, create_server), others noun_verb (server_action, server_cost), and singular/plural is inconsistent (list_servers vs get_server).
26 tools is a large surface for a VPS management server, especially since many have no descriptions and cover niche actions (e.g., notifications, payments). The count feels bloated and could be consolidated.
The tool set covers server lifecycle (create, delete, get, list), datacenters/tariffs/OS, SSH keys, and notifications/payments. However, the absence of descriptions for many tools leaves uncertainty about gaps, and an update or rename tool is missing or unclear.