Skip to main content
Glama
Kevin4562

mcp-qemu-lab

by Kevin4562
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-qemu-lab

No user-submitted related servers found.

    Related Servers

    • re-gdb

      Heretek-RE
      A
      license
      B
      quality
      C
      maintenance
      MCP server wrapping GDB and GEF for dynamic analysis, enabling interactive debugging and memory inspection via GDB/MI protocol.
      14
      1
      MIT

    • Rikune

      Last-emo-boy
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for reverse engineering Windows executables and related binary formats, offering static analysis, Ghidra-assisted function recovery, plugin-driven tooling, and optional isolated Windows runtime execution.
      3 npm
      242
      MIT

    • ghidraMCP

      albertlab0
      A
      license
      Not graded
      quality
      D
      maintenance
      An Model Context Protocol server that enables LLMs to autonomously reverse engineer applications by exposing Ghidra's decompilation and analysis tools. It allows AI agents to list code structures, rename methods, and analyze binaries directly through MCP-compatible clients.
      Apache 2.0

    • Protocol-SIFT-Async-Bridge

      mwarsss
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-grade, type-safe MCP server for memory forensics via Volatility 3, enabling LLM-assisted incident response without timeouts or evidence spoliation.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity, as they target specific actions on well-defined resources like VM operations, guest interactions, debugging, or process management. For example, vm_start, vm_stop, and vm_status are distinct lifecycle actions, while debugger_attach, debugger_continue, and debugger_detach are separate debugging steps.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as vm_start, guest_copy_in, debugger_attach, and process_list. This predictability makes it easy for agents to understand and select the right tool based on its naming convention.

    Tool Count4/5

    With 22 tools, the count is slightly high but reasonable for the comprehensive scope of QEMU lab management, covering VM lifecycle, guest operations, debugging, and process handling. It feels slightly heavy but each tool appears to earn its place without obvious redundancy.

    Completeness5/5

    The tool set provides complete coverage for the QEMU lab domain, including VM creation, start/stop/status, snapshot management, guest file operations, process debugging, and dependency checks. There are no apparent gaps that would hinder agent workflows, as all essential operations are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources