HyperDbg MCP Server
HyperDbg hypervisor-assisted debugging capabilities accessible to your LLM agents.
Data last scanned today · Reviewed today
Overview
The HyperDbg MCP Server provides a bridge between Model Context Protocol clients and the HyperDbg ring-0 debugger. By loading libhyperdbg.dll via ctypes, the server enables LLM agents to interact with hypervisor-assisted debugging tasks, including memory inspection, disassembly, and register state management. Users can operate in a local VMI mode or connect to a remote debuggee via serial, pipe, or network connections. To manage the inherent risks of ring-0 debugging, the server includes a mandatory read-only mode, per-call confirmation prompts for destructive operations, and an append-only audit log. Debuggee-sourced data is processed within an untrusted-data envelope to mitigate risks associated with analyzing potentially malicious targets.
Our verdict
With a security score of 35/100, this server is classified as high-risk. The evaluation is driven by its current status as a community-maintained project that has not yet been editorially reviewed, combined with the fact that it interacts directly with a ring-0 driver where errors can trigger system-level crashes. It is recommended for users working in isolated, non-production research environments who can thoroughly review the FFI implementation and audit logs, rather than those seeking a stable, vendor-verified integration.
- Zero direct dependencies reduce the supply-chain attack surface.
- Implements an append-only audit log for all tool calls.
- Wraps debuggee data in an untrusted-data envelope.
- Provides a explicit hard --read-only mode for safety.
- Operates with high-risk ring-0 privilege level via kernel drivers.
- FFI layer has not yet been validated against a live DLL.
- Community-maintained project with no formal vendor verification.
Tools
| Tool | Description | Risk |
|---|---|---|
| hd_mem_read | Reads memory from the debuggee. | low |
| hd_reg_read_all | Reads all registers from the debuggee. | low |
| hd_reg_read | Reads a specific register from the debuggee. | low |
| hd_eval | Evaluates an expression using HyperDbg. | low |
| hd_disasm | Disassembles memory at a given address. | low |
| hd_list_modules | Lists loaded modules in the debuggee. | low |
| hd_status | Retrieves the current status of the debugger. | low |
| hd_exec_continue | Continues execution of the debuggee. | medium |
| hd_exec_pause | Pauses execution of the debuggee. | medium |
| hd_exec_step | Steps execution of the debuggee. | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the host requirements to run this MCP server?
The server requires a Windows host with HyperDbg installed and its driver loaded, as it communicates with the hypervisor via libhyperdbg.dll.
›How can I prevent the server from executing destructive actions?
You can run the server with the --read-only flag, which prevents the registration of any write or script tools.
›Does the server provide any security measures when handling data from the debuggee?
Yes, all data sourced from the debuggee is wrapped in an untrusted-data envelope to ensure it is treated as inert by the LLM.
›Can I test the MCP server interface without having a HyperDbg installation?
Yes, you can use the --mock flag to exercise the tool surface without requiring an actual HyperDbg library or driver.
›How does the server handle sensitive or destructive debugger commands?
Target-mutating tools are gated behind per-call user confirmation via MCP elicitation to ensure intent before execution.
›Is there a way to track the operations performed by the server?
The server maintains an append-only audit log of every call, which can be configured via the --audit-log option.
Badge
Maintain this server? Add the live badge to your README.