Status: Internal. A working v1 reference implementation; a rewrite is planned. Apache-2.0. No public repository.
Drive the real tools directly, instead of through hand-built command lines and
pasted output.
What it is
Cupelix Manifold is the communication layer. It exposes reverse-engineering capability —
decompilers, debuggers, crash-dump triage, the emulator — to clients over one protocol, so a
GUI or an agent drives the actual tools rather than a transcript of them.
Deliberately protocol-agnostic
MCP is today’s transport. The name was chosen so that it does not have to be tomorrow’s: a
GUI plugin can reasonably want a different one, and the layer is built to allow that.
The same applies to what sits behind it. The layer abstracts over decompilers, not only
over transports — Ghidra is in scope alongside IDA. Five servers exist today, wrapping
headless disassembly, the emulator, crash-dump triage and user-mode debugging.
One detail worth publishing
The transport is a roughly 130-line MCP stdio implementation using nothing but the Python
standard library — zero dependencies. It was written because a dependency had no wheels for
Python 3.14. If you have the same problem, that approach is worth knowing about.
Status
What exists is a working v1 reference implementation, consolidated from three homes into
one in September 2026. A rewrite is planned. There is no public artefact, which is why this
page describes an approach rather than offering a download.