PyMemoryEditor
OfficialRelated Servers
Alternatives to PyMemoryEditor
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to programmatically control Cheat Engine for memory scanning, editing, cheat table management, and reverse engineering tasks.42MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform low-level Windows process memory research, including process attachment, memory scanning, reading/writing, pointer chasing, remote code execution, and inline hooking via MCP tools and Lua scripting.26 PyPI4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes dynamic binary instrumentation, memory editing, pointer scanning, and scripting capabilities to AI agents, enabling real-time process inspection and modification.MIT
- AlicenseCqualityBmaintenanceEnables an AI agent to auto-detect a game's engine (Unity, Unreal, Godot, Java, or native) from its files and then inspect, search, and patch the underlying binaries with in-process PE analysis, hex editing, pattern scanning, string extraction, checksums, diffing, and disassembly. Everything runs locally and offline with no cloud dependency or telemetry.1010058 npm4MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Cheat Engine 7.6 that enables AI agents to perform memory scanning, reading/writing, process manipulation, debugging, and code injection via a Lua named pipe bridge.4GPL 3.0
- AlicenseNot gradedqualityFmaintenanceEnables AI to directly control Cheat Engine for process attachment, memory scanning, reading/writing, address list management, speed hack, Lua/Auto Assembler execution, and CT file management via the MCP protocol.4MIT
TDQS
Scored across 14 tools
Every tool targets a distinct action in the memory-editing workflow: scan_value/refine_scan/scan_pattern each do different kinds of scans, read_value/write_value/list_scan_results are clearly separated, and pointer tools (find_pointer_paths vs resolve_pointer_chain) are explicitly framed as inverses. The descriptions reinforce the boundaries by describing how tools compose rather than overlap.
The set is overwhelmingly consistent verb_noun snake_case (scan_value, refine_scan, open_process, read_value, write_value, list_processes, resolve_pointer_chain). The only deviations are the two noun_info tools (process_info, server_info), which are internally consistent but break the verb_noun pattern.
14 tools is squarely in the sweet spot and each maps to a necessary step: process lifecycle, region/module inspection, scanning, refining, reading/writing, and pointer resolution. No tool looks redundant or throwaway for a Cheat Engine-style server.
The surface covers the full lifecycle: discover/attach/close processes, page memory regions and results, first-scan and refine-scan, AOB scanning, read/write with reversibility, and pointer discovery plus replay for persistence across restarts, with server_info exposing limits and open sessions. No obvious dead ends or missing operations for the stated domain.