pickfit

BrowseDeveloper CLIs

Corvus

MCP server and CLI to decompile, analyze, compare and patch .NET and native binaries.

Tested on macOS and Linux

Use it

macOS arm64

  1. download install script

    curl -fsSL https://raw.githubusercontent.com/Albasha0x0/Corvus/main/install.sh -o /tmp/corvus-install.sh && ls -l /tmp/corvus-install.sh && wc -l /tmp/corvus-install.sh
  2. install Corvus 2.9.0 via script with --yes

    sh /tmp/corvus-install.sh --yes
Where the README and reality differ
  • README: corvus decompile_member --load app.dll member=Ns.Type::Method
    What worked: CLI help shows tools expect image= parameter; --load flag was not accepted as shown and resulted in missing required parameter 'image' error (commands 14,15). Installer still works and corvus --help lists tools.

Check that it works

file /tmp/hello

The output should contain “Mach-O 64-bit executable arm64”.

First thing to try

cat > /tmp/hello.c <<'EOF'
#include <stdio.h>
const char *msg = "HelloCorvus";
int add(int a, int b) { return a+b; }
int main(){ printf("%s %d\n", msg, add(2,3)); return 0; }
EOF
cat > /tmp/hello_v2.c <<'EOF'
#include <stdio.h>
const char *msg = "HelloCorvusV2";
int add(int a, int b) { return a+b+1; }
int sub(int a, int b) { return a-b; }
int main(){ printf("%s %d %d\n", msg, add(2,3), sub(5,2)); return 0; }
EOF
clang /tmp/hello.c -o /tmp/hello -g
clang /tmp/hello_v2.c -o /tmp/hello_v2 -g
ls -l /tmp/hello /tmp/hello_v2
file /tmp/hello

Run corvus list_functions image=<binary> limit=5 to list the first functions in a binary.

Linux x86_64

  1. download install script for reading

    curl -fsSL https://raw.githubusercontent.com/Albasha0x0/Corvus/main/install.sh -o /tmp/corvus-install.sh
  2. install Corvus via script with --yes

    sh /tmp/corvus-install.sh --yes
Where the README and reality differ
  • README: curl -fsSL .../install.sh | sh
    What worked: download to /tmp/corvus-install.sh, read it, then run sh /tmp/corvus-install.sh --yes for non-interactive install with no MCP client
  • README: corvus decompile_member --load app.dll member=Ns.Type::Method
    What worked: native calls need image=/bin/ls plus an address from list_functions; disassemble address=main fails on stripped /bin/ls; --load alone leaves image missing

Check that it works

corvus --help

The output should contain “Tool exit codes: 0 success”.

First thing to try

corvus list_functions image=/bin/ls limit=5

Run corvus list_functions image=<binary> limit=5 to list the first functions in a binary.

What it does

  • Search binaries and show cross-references
    How to use it
    1. Run corvus find_xrefs image=<binary> address=<address> to list references to an address.
    2. Read the count and the listed references in the output.
    Tested
  • Decompile .NET and native binaries
    Not shown working
  • Compare builds
    Not tested
  • Patch binaries and save a patched copy
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • decompile .NET and native binaries
  • explain how a DLL builds its export file
  • inspect functions, disassembly and cross-references
  • compare builds
  • review diff and save patched copy

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 2.9.0

Differences the test machine hit

  • README: curl -fsSL https://raw.githubusercontent.com/Albasha0x0/Corvus/main/install.sh | sh
    In the test: Downloaded script first to /tmp/corvus-install.sh and ran sh /tmp/corvus-install.sh --yes; script verifies SHA256SUMS and provenance, installed to ~/.local/share/Corvus/versions/2.9.0

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 2.8.0

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.