No user-submitted related servers found.
Scored across 14 tools
Most tools have clear resource/action boundaries across the guest lifecycle, such as acquire, stage, script, image, finish, and release. However, relay_probe and relay_status both report session/guest state, and relay_extract overlaps somewhat with relay_finish's extraction phase, so an agent may hesitate between these pairs despite the detailed descriptions.
All tools use a consistent relay_ prefix and snake_case naming. The console tools form a predictable relay_console_resolve/open/cancel group, and the few noun-only names like relay_status and relay_image remain readable and consistent with the overall convention.
Fourteen tools is well within the appropriate range for a VM relay server with discovery, lifecycle, evidence, and console-sharing concerns. Each tool maps to a distinct phase or safety boundary, and the console trio is justified by the need to resolve, open, and cancel viewing attempts separately.
The surface covers the full guest lifecycle: discovery, acquisition, staging, scripted execution, image and extraction evidence, completion/release, status, and console viewing. A minor gap is the lack of an explicit tool to list all available images or durable machines independently of app-name search, leaving some discovery dependent on relay_search and relay_probe output.