No user-submitted related servers found.
Scored across 31 tools
Tool names and descriptions generally separate resources and actions well, but a few overlapping boundaries remain: read_service_logs can already fetch Docker logs, duplicating get_docker_container_logs, and list_virtual_hosts/get_open_ports both surface listening-port info. Overall an agent can usually pick the right tool with careful reading.
Every tool follows a snake_case verb_noun pattern with semantically appropriate verbs such as list, check, get, audit, test, execute, and create. Even with a large surface, the prefixes map predictably to action types and the resource nouns are clear.
31 tools is a heavy single-server surface and exceeds the 25+ threshold for comfortable agent selection. Several tools could be consolidated, such as Docker logs vs. service logs, or system health vs. separate status/disk tools.
The server has strong coverage for monitoring, auditing, Docker, config files, and whitelisted recovery actions, but there are notable dead ends: backups can be created but not restored, SSH config is audited but cannot be edited, and UFW/SSL have no modification or renewal path. These gaps will force agents to stop or go outside the MCP for common VPS remediation tasks.