VPSnet
Related Servers
Alternatives to VPSnet
No user-submitted related servers found.
Related Servers
AlicenseBqualityDmaintenanceManage Hostodo VPS infrastructure from MCP clients and AI agents with scoped tokens and audit logs.47MIT- AlicenseNot gradedqualityBmaintenanceEnables read-only inspection and confirmed mutation operations on a single VPS over SSH, including host health, Docker, Compose, Swarm, firewall, and system debugging tools.46 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables ChatGPT, Claude, and Cursor to securely manage a VPS through filesystem operations, system monitoring, and long-horizon command execution, protected by OAuth 2.1 with PKCE.-
- AlicenseNot gradedqualityDmaintenanceEnables remote command execution and file management over SSH and SFTP, supporting persistent connection storage and automated discovery for BinaryLane VPS servers.15,194 npm2MIT

@vertracloud/mcpofficial
AlicenseBqualityAmaintenanceEnables 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.138476 npm2MIT- AlicenseAqualityDmaintenanceEnables AI assistants to manage VPS servers, domains, DNS records, and SSH keys through the VPS.org API via natural language.262MIT
TDQS
Scored across 334 tools
The set covers many distinct resources, but with 334 tools there is heavy overlap between generic and specific actions (e.g. manage_application vs start/stop/restart/uninstall, manage_certificate vs cancel/reissue/recheck, multiple quote/renew/order paths for network products and addresses). An agent must read long descriptions to choose safely, and several families contain multiple plausible entry points.
Almost all tools use snake_case verb_noun names (list_*, get_*, create_*, set_*, quote_*, order_*, delete_*), so the pattern is predictable. Minor inconsistencies come from scope prefixes and generic manage_* tools that coexist with explicit action tools.
334 tools is far beyond the 3-15 well-scoped range and exceeds the 50+ extreme threshold. Even though the provider domain is broad, this surface cannot be reliably navigated in a single MCP server.
The surface covers CRUD/lifecycle for services, networking, DNS, domains, certificates, managed applications, backups, functions, billing, SSH keys, and more, with intentional security omissions documented. No obvious required operation is missing for the provider's advertised scope.