A
licenseNot graded
qualityC
maintenanceA read-only MCP server providing SQLite querying, port checking, and git diff summary tools for local development.
MIT
RE-MCP
Related Servers
Alternatives to RE-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP 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.0240MIT
- AlicenseAqualityCmaintenanceA safety-first local MCP server that enables bounded file reading, text search, line-range editing with optimistic locking, and read-only git diff operations within a single code workspace.6MIT
- AlicenseNot gradedqualityBmaintenanceSafe local MCP server for Windows to list, read, search, patch, backup, and verify code files in allowed folders, with Git integration and dry-run diffs.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes Python debugging tools backed by debugpy, providing a focused debugging surface for local scripts.11MIT
- AlicenseNot gradedqualityBmaintenanceA 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.31 npmMozilla Public 2.0
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
ActivityStale
ResponsivenessNo issues