Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Reverse Engineer Anything (Docker)

OCI · DOCKER.IO/PSYB0T/REVERSE-ENGINEER-ANYTHING

REA reverse-engineering MCP server in Docker, with JADX, Apktool and adb for APKs.

9 Trust /100

Last scanned (12 hours ago)

Scores higher than 23% of OCI servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result. View diagnostics → Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (WTFPL AND MIT AND Apache-2.0 AND GPL-2.0-only WITH Classpath-exception-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 9

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Analysed oci/docker.io/psyb0t/reverse-engineer-anything@v0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Vulnerabilities 19 ungraded findings

From the publisher's SBOM, not graded. These advisories match packages listed in the SBOM the publisher attached to this image. A publisher naming a vulnerable package in their own image is credible, so we show them. Nothing verifies that SBOM, though, so the Known CVEs signal does not grade the image from it.

ID CVE Severity Vector Fix available
GHSA-6j4f-fj2g-mc7p CVE-2026-102276 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q2hr-2g5m-vwhr CVE-2026-102277 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-qhr7-859c-m2p7 CVE-2026-102278 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-ch52-4w7c-c8xp CVE-2026-93748 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N no
GHSA-2vr4-cq9g-pvrc CVE-2026-101910 medium yes
GHSA-h3mg-xc3c-68pw CVE-2026-101911 medium yes
GHSA-j6r3-76f7-8jcv CVE-2026-101912 medium yes
GHSA-rpw4-54j3-4h4q CVE-2026-101913 medium yes
GHSA-4328-8hgf-7wjr CVE-2019-16777 high CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N yes
GHSA-93f3-23rq-pjfp CVE-2020-15095 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N yes
GHSA-m5h6-hr3q-22h5 CVE-2016-3956 high yes
GHSA-m6cx-g6qm-p2cx CVE-2019-16775 high CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N yes
GHSA-ph34-pc88-72gc CVE-2018-7408 high CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H yes
GHSA-v3jv-wrf4-5845 CVE-2013-4116 low yes
GHSA-x8qc-rrcw-4r46 CVE-2019-16776 high CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N yes
GHSA-rj75-hqrm-r3gf CVE-2026-104844 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-3wwx-pv8p-q78v CVE-2026-85024 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-r53p-7pc4-xj5r CVE-2026-18540 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-rfgv-xxqx-mfg5 CVE-2026-19534 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · docker.io/psyb0t/reverse-engineer-anything

# install command
$ docker pull docker.io/psyb0t/reverse-engineer-anything:v0.1.1
Common questions

What is the Reverse Engineer Anything (Docker) MCP server?

Reverse Engineer Anything (Docker) is an MCP server listed in the public MCP registry as io.github.psyb0t/reverse-engineer-anything. REA reverse-engineering MCP server in Docker, with JADX, Apktool and adb for APKs. This page covers its container image (docker.io/psyb0t/reverse-engineer-anything).

Is the Reverse Engineer Anything (Docker) MCP server safe to use?

Reverse Engineer Anything (Docker) scores 9 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 19 known advisories as of 18 October 2026. We do not grade that SBOM, as nothing verifies it. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Reverse Engineer Anything (Docker) MCP server still maintained?

Reverse Engineer Anything (Docker) is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.