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.

io.github.hellosverre/ghidralens

NPM · GHIDRALENS · SCANNED SEP 20

Interactive Ghidra views in your AI client: decompile, rename, and navigate a binary.

Available components

+4 this week 81 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 683 tokens (~52/item across 13 items; 10 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 40% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the io.github.hellosverre/ghidralens MCP server?

io.github.hellosverre/ghidralens runs locally as an npm package, launched with npx -y ghidralens. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ghidralens

# add to Claude Code
claude mcp add hellosverre-ghidralens -- npx -y ghidralens
// .cursor/mcp.json
{
  "mcpServers": {
    "hellosverre-ghidralens": {
      "command": "npx",
      "args": [
        "-y",
        "ghidralens"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hellosverre-ghidralens": {
      "command": "npx",
      "args": [
        "-y",
        "ghidralens"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hellosverre-ghidralens -- npx -y ghidralens
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hellosverre-ghidralens": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ghidralens"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hellosverre-ghidralens --command npx --arg -y --arg ghidralens
# ~/.hermes/config.yaml
mcp_servers:
  hellosverre-ghidralens:
    command: "npx"
    args: ["-y", "ghidralens"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hellosverre-ghidralens": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "ghidralens"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hellosverre-ghidralens -t stdio -c npx -a -y ghidralens
// mcp.json
{
  "mcpServers": {
    "hellosverre-ghidralens": {
      "command": "npx",
      "args": [
        "-y",
        "ghidralens"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Sept 26 +4
    • Stability: unverified → 0.27 functional
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 20 Sept 2026 · Analysed npm/ghidralens@0.1.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 97 packages
Packages resolved 97
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~559 tokens

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 →

Tool Tokens
add_comment ~52

Attach a plate comment at an address. Persists into the Ghidra project, so notes made here show up in the Ghidra GUI.

NameTypeReqDescription
addressstringyes
textstringyes

No output schema declared.

No examples provided.

call_graph ~57

Draw the callers and callees around one function as a navigable graph. Depth is capped at 3 because call graphs fan out exponentially.

NameTypeReqDescription
addressstring
depthinteger
namestring

No output schema declared.

No examples provided.

decompile ~67

Decompile one function to C and show it in an interactive view. Identify the function by address (hex) or by name.

NameTypeReqDescription
addressstringEntry point, e.g. 0x140001000
namestringFunction name, e.g. main

No output schema declared.

No examples provided.

find_strings ~47

Search defined string data. Usually the fastest way into an unknown binary - find the message, then look at what references it.

NameTypeReqDescription
limitinteger
querystring

No output schema declared.

No examples provided.

list_functions ~66

Browse the program's functions in a sortable table. Filter by substring; sort by address, name, size or caller count.

NameTypeReqDescription
limitinteger
offsetinteger
querystringCase-insensitive name filter
sortstring

No output schema declared.

No examples provided.

open_binary ~80

Load an executable into the Ghidra session and run auto-analysis. Slow the first time for a given file (seconds to minutes); cached in the Ghidra project afterwards. Must be called before anything else.

NameTypeReqDescription
analyzebooleanRun auto-analysis. Only set false if already analysed.
pathstringyesAbsolute path to the executable

No output schema declared.

No examples provided.

program_info ~20

What is currently open: format, architecture, function count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

rename_symbol ~92

Rename a function, or a local variable inside one. Pass old_name to rename a local; omit it to rename the function itself. This is what a click on an identifier in the decompiler view fires.

NameTypeReqDescription
addressstringyesAddress of the function that owns the symbol
new_namestringyes
old_namestringCurrent local-variable name. Omit to rename the function.

No output schema declared.

No examples provided.

save_program ~37

Write renames and comments back to the Ghidra project on disk. Nothing is lost without this, but nothing is durable with it either.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

xrefs_to ~41

Everything that references an address.

NameTypeReqDescription
addressstringyesTarget address, e.g. 0x140001000
limitinteger

No output schema declared.

No examples provided.

Common questions

What is the io.github.hellosverre/ghidralens MCP server?

io.github.hellosverre/ghidralens is an MCP server listed in the public MCP registry as io.github.hellosverre/ghidralens. Interactive Ghidra views in your AI client: decompile, rename, and navigate a binary. This page covers its npm package (ghidralens).

Is the io.github.hellosverre/ghidralens MCP server safe to use?

io.github.hellosverre/ghidralens scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.

What tools does the io.github.hellosverre/ghidralens MCP server expose?

io.github.hellosverre/ghidralens exposes 10 tools: open_binary, program_info, decompile, list_functions, call_graph, and 5 more. Their descriptions and schemas cost roughly 559 tokens of context every time the server is loaded.

Is the io.github.hellosverre/ghidralens MCP server still maintained?

io.github.hellosverre/ghidralens is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.hellosverre/ghidralens MCP server under?

io.github.hellosverre/ghidralens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.