bitslicer-mcp
Related Servers
Alternatives to bitslicer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLocal MCP server enabling Codex and ChatGPT to read/write files, execute commands, manage processes, use Git, and inspect images on the user's machine with full privileges.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA macOS-native MCP server that provides AI hosts with fresh workspace state, bounded context, and retained execution evidence, avoiding collapsing operations into shell strings.171 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceA Linux-native MCP server that gives AI assistants direct access to DMA-based memory operations for memory inspection, process analysis, reverse engineering, and game engine SDK extraction via natural language.13AGPL 3.0
- FlicenseNot gradedqualityAmaintenanceA safety-first MCP server enabling file inspection/editing, allowlisted command execution, process listing, and optional desktop automation. It emphasizes security with disabled writes/commands/GUI by default and local feature gates.1-
- AlicenseNot gradedqualityDmaintenanceAn MCP server providing LLM clients with structured, transaction-safe access to Hopper-derived reverse-engineering snapshots, enabling binary analysis without the disassembler in the model's context window.1MIT
- AlicenseNot gradedqualityBmaintenanceA local, privacy-first MCP server that orchestrates Ghidra, Binary Ninja, x64dbg, and system tools to provide AI assistants with powerful binary analysis capabilities.Academic Free v1.1
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose: attach/list processes, read/dump memory, scan/filter, edit session phases, and utility functions. The only close pair is read_memory vs dump_memory, but descriptions clearly distinguish by size and encoding.
All tools follow a consistent snake_case verb_noun pattern (e.g., list_memory_regions, apply_memory_patch, resolve_pointer_chain). Standalone verbs like ping, attach, and disassemble are also in snake_case and fit the convention.
16 tools is slightly above the typical 3-15 range for a well-scoped server, but every tool serves a distinct function in the memory editing workflow. The count feels justified by the domain's complexity.
Covers process attachment, memory enumeration/reading, scanning/filtering, pointer resolution, disassembly, and a safe patch workflow with preview/apply/undo. Missing an explicit detach tool, and writes are restricted to previewed patches, but the core lifecycle is well covered.