How Bootscry compares
Several projects now let an agent see and drive a machine through a KVM. We do not say nobody else does this. We lead with real-hardware evidence and a published method. We have run only our own Comet prototype and have not run most of the projects below.
What we lead with
- Real-hardware evidence. Every claim links to a record from a real Comet and real target machines. Failures and manual steps are listed on the usage page.
- Boot-menu catching. Bootscry taps a key through boot and watches the video drop out, instead of waiting a fixed time. It is measured on one AMI BIOS in the boot-menu record. As we read its code, kvm-pilot waits a fixed time and then taps a set number of times.
- An exact reader with a phrase list. A local vision model reproduced verbatim phrases better than two OCR engines: 31 of 32 phrases, against 22 and 16. The sample is small (4 frames, 32 phrases, one model), so treat it as a lead, not a rate.
- A published method. Each number on this site links to the record it came from, with its limits.
What we do not claim
Capability tiers, audit logs, read-only modes, stale-frame refusal and an untrusted-screen-text rule are not differences. Other projects below have most of them. A general-purpose agent with a KVM driver can already read a settled BIOS screen. GlassOnTin/glkvm-mcp lists local OCR with boxes and click-on-text, which overlaps with ours. We have not run it. Our safety controls are described on the safety page and their gaps on the threat model.
Project scope and published code
| Project | Published focus | Code and license | Facts and date | Our lab status |
|---|---|---|---|---|
| Bootscry | Agent observation and control through video KVM, with serial, camera and other channels planned. The Comet KVM is the working reference. | Public repository and license planned. | As of October nineteenth, 2026: two KVM models run (the Comet is the measured reference; the Sipeed NanoKVM has first runs on one unit), one firmware each, one lab. A Dell iDRAC9 screenshot driver has run on one server, and a VNC driver against QEMU only. A JetKVM is set up with no driver yet. | Comet prototype measured. See also recorded uses. |
| kvm-pilot | Agent control across KVM, BMC and SSH, as described by its maintainers. Its source classes tools by effect, asks for approval on input, and refuses a click on a stale frame. | Apache 2.0 repository. | As of October fifteenth, 2026: version 1.0.0 is on the package index and the MCP registry. Its changelog reports live runs on three device types and emulator-only runs for the rest. | Not run by Bootscry. |
| TinyPilot | Browser-based KVM appliance. Its REST API needs a yearly Automation License. Its MCP server, tinypilot-mcp, is MIT licensed and drives that paid API. | Server repository is MIT licensed. | As of October fifteenth, 2026, from the repositories and the vendor automation page. | Not run by Bootscry. |
| Sipeed NanoKVM | Network KVM device and software. Press coverage of the NanoKVM-Go crowdfunding says every KVM function is exposed as an MCP server. That is the vendor claim as reported, and we have not read the product. | Repository is GPLv3. Press: It's FOSS. | As of October fifteenth, 2026. | Not run by Bootscry. |
| Lantronix Percepxion MCP | A vendor blog describes an MIT-licensed MCP server for serial and out-of-band access to network devices. It says writes are off by default and commands are logged. It works on console access, not on a video feed. | MIT, per the vendor blog. | As of October fifteenth, 2026. The blog is dated May 2026. | Not run by Bootscry. |
| GlassOnTin/glkvm-mcp | A Python MCP server for GL.iNet KVMs. Its README lists local OCR with pixel boxes, click-on-text and a frame hash for freshness. It is tested on a different GL.iNet model, not the Comet. | AGPL-3.0, so we cannot copy its code. | As of October fifteenth, 2026: created in October 2026, one star, README claims only. | Not run by Bootscry. We plan to test it by behaviour, never by reading its code into ours. |
| jetkvm-mcp | A community MCP server for JetKVM over WebRTC. It is not made by JetKVM. | MIT. | As of October fifteenth, 2026: last pushed in September 2026. | Not run by Bootscry. |
| PiKVM | Remote KVM hardware and software stack. | KVMD is GPLv3 or later. | As of October fifteenth, 2026. | Not run by Bootscry. |
| JetKVM | Remote KVM appliance and device software. | Device software is GPL-2.0. | As of October fifteenth, 2026. | Not run by Bootscry. |
Facts come from each project's public pages and from our research notes. Dates show when we last read them. Please check the linked page before relying on any row. Licenses refer to the linked software repositories. Hardware, cloud services and automation features may have separate terms. We have not benchmarked these products against one another, and we have not run most of them.
Standing on Prior Work
Bootscry's safety work is informed by kvm-pilot. Its Comet client works with the device's KVMD-derived API; PiKVM publishes the upstream KVMD project.
The current Bootscry evidence covers local OCR, input delivery, and a BIOS catch. They come from one Comet used on eight machines in one lab (a NAS, PCs, ARM boards and a Raspberry Pi); each record says which machine or machines it covers, and most cover one. First runs of a second KVM family are recorded separately. A shared driver layer has drivers for five kinds of device. Three have run on real hardware, one unit each: the Comet, a Sipeed NanoKVM and a Dell iDRAC9 (screenshots only). The VNC driver has run against QEMU only, and the PiKVM client against PiKVM's software in a container. Boot-phase detection is in the code and is not yet in the measured evidence.