Skip to main content
Glama
79cbd8hmgj-wq

RE-MCP

by 79cbd8hmgj-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to RE-MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • mcp-mgba

      Canadadry
      A
      license
      Not graded
      quality
      B
      maintenance
      A headless MCP server that lets an LLM load Game Boy Advance ROMs, step through instructions, read and write memory, and manage breakpoints, watchpoints, and registers.
      29 npm
      Mozilla Public 2.0

    • gdb-multiarch-mcp

      sbergeron42
      A
      license
      B
      quality
      D
      maintenance
      An MCP server providing direct access to gdb-multiarch for debugging Nintendo Switch executables on Yuzu or hardware via a GDB stub. It features specialized tools for offset-based breakpoints, instruction patching, and frame-pointer backtraces relative to the game's base address.
      33
      3
      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

    B3.1/5.0

    Scored across 52 tools

    Disambiguation4/5

    The tools are clearly organized by domain prefix (bakugan_, nds_, desmume_, controller_), and each tool description specifies a distinct operation. A few tool pairs like nds_list_references vs nds_ghidra_list_references or nds_resolve_rom_offset vs nds_resolve_runtime_address could be initially confused, but the descriptions draw clear boundaries.

    Naming Consistency5/5

    All tool names use lowercase snake_case with a verb_noun pattern and consistent domain prefixes (e.g., nds_, desmume_, controller_). Exceptions like get_project_status, run_project_verification, and server_capabilities still follow the same snake_case verb-first convention, so the overall pattern is highly predictable.

    Tool Count1/5

    With 52 tools, the server is far beyond the 'too many' threshold and approaches the 'extreme mismatch' range. Even though the reverse-engineering domain is complex, the sheer number forces an agent to navigate a large surface, making the set feel bloated rather than well-scoped.

    Completeness4/5

    The tool set covers the core workflows of NDS static analysis, emulator debugging, mutation validation/building, Ghidra integration, and project status—all within a clearly defined safety boundary. Minor gaps like no explicit memory-write debugger tool exist, but these appear intentionally omitted for safety, so the surface is reasonably complete for its purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources