Skip to main content
Glama

Reversium

reversium.com · Reverse engineer everything. Jailbreak, but for everything else.

An MCP server and agent skills that turn anything you lawfully have into a saved, versioned blueprint and run a build-and-compare loop until your version stands on its own. Software goes to REA (MIT). Devices, film and ads, editing styles, viral formats, companies and your own site are Reversium's.

/reverse ./vendor-app.apk          → blueprint v1 (REA does the unpacking)
/reverse "my wireless mic → iPhone" → device method: link, capture plan, bridge, parts
/reverse https://…/spot.mp4         → ad method: cuts, rhythm, lenses, sound, shot list
/loop wireless-mic-phone            → your build vs. the blueprint; one change
/blueprint diff wireless-mic-phone 1 3
/teardown publish wireless-mic-phone

Every run ends in the same document shape: TARGET · INSIDE · FOUND · PLAN · LOOP · RULES, plus domain keys like TRAFFIC, CUTS, REACH, PARTS.

Install

Requires Node 20+ or Bun. Until the first npm publish, run from a clone: bun install && bun run build, then point your MCP client at bin/reversium.js.

npx reversium           # after publish; or: bunx reversium

Claude Code, .mcp.json in your project:

{ "mcpServers": { "reversium": { "command": "npx", "args": ["-y", "reversium"] } } }

Skills: copy skills/ into .claude/skills/ (or install this repo as a plugin). /reverse is the entry point; /reversium and /rev are aliases.

Related MCP server: DDAG MCP

What it does that a chat window doesn't

  1. The blueprint persists and versions. ./.reversium/blueprints/<slug>/v001.md … Markdown for you, JSON for tools. blueprint_diff shows what you learned.

  2. The loop measures. loop_compare lines your attempt up against the reference section by section and hands back exactly one change. When there are no gaps left, it asks where yours should diverge on purpose.

  3. The rules are code. Every blueprint needs a lawful-access attestation in your own words. Security reads need ownership proof first. Refusals cite the clause in AUP.md.

Tools

tool

what

target_classify

path / URL / phrase → domain, skill, whether REA should take it

blueprint_create · get · update · diff · list

the saved, versioned document

loop_compare

one round: attempt vs. reference, one change, saved

rea_handoff

writes a REA task file for software targets

own_site_challenge · verify · headers

prove you own a domain, then one read-only headers check

teardown_render

blueprint → static page for reversium.com

What it won't do

Work around access controls or DRM. Touch safety or flight-restriction systems. Log in anywhere or read behind a login. Probe a site you haven't proven you own. Reproduce the target. See AUP.md; the server enforces the parts it can.

Local-first

Nothing leaves your machine. No accounts, no telemetry, no cloud. teardown_render writes a file; publishing it is your move.

Develop

bun install
bun run smoke      # starts the server over stdio and exercises every tool in a temp dir
bun run build      # dist/index.js for the npm bin

Status

v0.1. Built on REA. Trademark and name clearance pending. First public teardown: coming.

Apache 2.0. See LICENSE and NOTICE. "Reversium" is a name, not part of the licence grant.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to trace regulatory rule changes to affected parties and required actions through deterministic safety gates, returning dated action plans and hash-linked evidence records. Supports 12 MCP tools over stdio or streamable HTTP for source comparison, obligation decomposition, scope assessment, planning, and evidence validation across multiple domain packs.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Turns a build or audit target into a graph of claims that a coding agent must decompose and verify bottom-up against evidence, with judgments pinned to git commits and file hashes and findings recorded as issues on the claims they refute. It keeps an append-only, replayable record of every operation, exposes the standing and frontier of the work, and flags stale judgments when cited code changes.
      10 npm
      4
      MIT