Skip to content
Back to search

HopperMCP

A Model Context Protocol server for Hopper Disassembler

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mxiris-reverse-engineering--hoppermcp/badge.svg)](/listings/mxiris-reverse-engineering--hoppermcp)

HTML

<a href="/listings/mxiris-reverse-engineering--hoppermcp"><img src="/api/listings/mxiris-reverse-engineering--hoppermcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 49 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # HopperMCP
  2. ## Overview
  3. A [Model Context Protocol](https://modelcontextprotocol.io/introduction) server for `Hopper Disassembler` interaction and automation. This server provides tools to read and write `Hopper Disassembler` files via Large Language Models.
  4. Please note that `HopperMCP` is currently in early development. The functionality and available tools are subject to change and expansion as we continue to develop and improve the server.
  5. ## Note
  6. Due to Hopper's closed environment, it doesn't allow plugins to link to any third-party libraries, only permitting the use of basic dependencies like `Foundation` and `AppKit`. Therefore, we need to inject code into Hopper to enable loading of any type of plugin.
  7. Hopper's SDK is also very simple, with no public interfaces to obtain disassembled or decompiled code. We've reverse-engineered Hopper and call its private interfaces to access this essential information. These basic interfaces are generally stable, but there's no guarantee that the author won't modify them in future versions.
  8. Since code injection is required, you must disable **SIP** (System Integrity Protection) to use `HopperMCP`.
  9. ## Usage
  10. 1. Move `HopperMCP.app` to your Applications folder
  11. 2. Install the Helper program (option 1 in the `HopperMCPApp` main interface, requires password)
  12. 3. Install the plugin to the specified directory (option 2 in the `HopperMCPApp` main interface)
  13. The application needs to run in the background. You should launch `HopperMCP` before starting `Hopper` (when `HopperMCP` detects Hopper starting, it will automatically inject code)
  14. About 3 seconds after Hopper launches, you'll see a `Tool Plugin` menu appear in the menu bar. `HopperMCP` provides 4 menu options:
  15. - `Start MCP Plugin`
  16. - Starts the MCP plugin service
  17. - `Stop MCP Plugin`
  18. - Stops the MCP plugin service
  19. - `Reload Plugins`
  20. - Reloads all tool plugins
  21. - `Notify Document Loaded`
  22. - Since plugins can't detect when Hopper has finished loading, you need to manually notify the plugin when the document has loaded completely. This will initiate some caching operations. Because Hopper doesn't provide an interface to find addresses by name, we need to handle this ourselves.
  23. 4. Start the `HopperMCP` plugin service
  24. 5. Copy the `Hopper MCP Server` JSON (option 3 in the `HopperMCPApp` main interface) and input this JSON into your MCP client
  25. Now you can use `HopperMCP`!
  26. ## Available Tools
  27. - Get current assembly/pseudocode
  28. - Get assembly/pseudocode by name
  29. - Get assembly/pseudocode by address
  30. - Add comment
  31. - Add inline comment

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.