pickfit

BrowseMCP servers

Super Trouper

MCP server exposing Frida reverse-engineering toolkit capabilities to coding agents.

Tested on Linux

Use it

Linux x86_64

  1. Install super-trouper via npm

    npm install -g @crissyfield/super-trouper

Check that it works

super-trouper --help

The output should contain “MCP server for the Frida”.

Add it to your agent

claude mcp add super-trouper -- super-trouper
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "super-trouper": {
      "command": "super-trouper",
      "args": []
    }
  }
}

Add super-trouper as an MCP server in your coding agent's settings, then ask the agent to list devices to confirm it works.

What it does

  • Connect to local, USB, and remote devices
    Not shown working
  • Attach to apps and processes
    Not tested
  • Create and load instrumentation scripts
    Not tested
  • Search and fetch community scripts from CodeShare
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • connect to local, USB, and remote devices
  • inspect applications and processes
  • load and evaluate JavaScript instrumentation scripts
  • search and fetch community scripts from Frida CodeShare
  • list modules loaded in an attached process

How pickfit tested it

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

Linux x86_64

An MCP client called one of its tools

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

An MCP client handshake over stdio listed 38 tools, and a call to device_list returned a result.

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.