DesktopManager Windows Verification runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Oct 2026.
Inspect and verify Windows x64 desktop apps through a local, read-only-by-default MCP server.
What the code does
We read the source, 2 h ago · rules ccca72095570
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
using var proc1 = Process.Start("notepad.exe");
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
using var proc1 = Process.Start("notepad.exe");
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch DesktopManager Windows Verification and you get told the day something new turns up.
Alternatives to DesktopManager Windows Verification
same job, measured the same wayWindows UI Automation MCP server for desktop inspection and element lookup. Windows only.
Inspect and drive Avalonia, WPF and MAUI desktop applications through local MCP.
Local macOS 27 desktop automation through MCP on Apple silicon.
95 typed Typesense operations for AI agents through an MCP server that is read-only by default.
95 typed Typesense operations for AI agents through an MCP server that is read-only by default.
Task automation via SQLite, desktop Local API, or Mindwtr Cloud; read-only by default.
Start, stop, and inspect local dev servers in a desktop app instead of the agent's session.
Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.
DesktopManager Windows Verification — questions
Answers built from our own checks of this server.