rea_patch_server
Related Servers
Alternatives to rea_patch_server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables applying unified diff patches to files with comprehensive security validation, automatic backup/rollback, and atomic multi-file operations. Provides 7 tools and 4 error recovery patterns for safe patch management workflows.2MIT
- AlicenseBqualityBmaintenanceEnables agents to perform bounded binary-file inspection, hashing, search, and diffing within configured roots, and to preview and apply expected-byte-validated patches that produce new output copies while preserving originals. It also reads a user's existing GUI session—active buffer context, selections, and unsaved in-memory bytes—through trusted templates, with mutations to live buffers explicitly disabled.142MIT
- AlicenseAqualityCmaintenanceMCP server for on-disk patching of binary artifacts with SHA-256 manifest, byte-level patch application, and manifest-driven restore, ensuring auditability and reversibility.4MIT
- 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.1010055 npm5MIT
- AlicenseNot gradedqualityDmaintenanceEnables precise file patching using SEARCH/REPLACE blocks, with mandatory directory sandboxing, automatic Python QA (Ruff/Black/MyPy), and git versioning for rollback.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable agents to locate game save files, identify their engines, compute unlock plans for gallery/recollection flags, diff saves, and safely dry-run, apply, verify, or roll back reversible byte patches with automatic backups.MIT
TDQS
Scored across 12 tools
The set cleanly splits into binary-patch tools (pe_info, dump, va_to_offset, apply, verify, restore, sha256) and text-patch tools (text_view, text_search, text_apply, text_verify, text_restore), with the text_ prefix making the split obvious. The only real overlaps are that rea_patch_pe_info also reports SHA-256 (duplicating rea_patch_sha256), and verify/restore exist in both halves without names that scream which is which at a glance.
All tools use the rea_patch_ snake_case prefix with clear verb/noun endings, so the pattern is predictable. The asymmetry is that only the text family gets the text_ qualifier while binary tools are unprefixed (rea_patch_apply vs rea_patch_text_apply), which is mildly inconsistent but still readable.
Twelve tools is squarely in the well-scoped range, and each tool maps to a distinct step in the patch workflow (inspect, locate, apply, verify, restore) for both binary and text files. No tool feels redundant or padding.
Both halves cover a full patch lifecycle: inspect (pe_info/dump/text_view), search (text_search), transform (apply/text_apply), verify (verify/text_verify), and rollback (restore/text_restore), plus address math and hashing. The main gap is a binary byte-pattern/signature search — an agent hunting bytes must fall back to repeated dump calls, since only the text family has a search tool.