Ghidra MCP Server

@cylixlee/ghidra-mcp npm v0.2.1 Source verified

Published by cylixlee — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Trust grade
A
100/100
Last scanned
Trust
A · 100/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 100/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 0 = 100. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
capability blast radius (minimal) — client exposure if the model is manipulated
publisher verification (provenance) — cryptographic build provenance ties the artifact to its source
inspection depth (source) — how much of the target the scan could see

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 27

Each tool and what it can reach — statically extracted from the published source.

  • decompile_functionno sensitive capability
  • decompile_function_by_addressno sensitive capability
  • disassemble_functionno sensitive capability
  • get_current_addressno sensitive capability
  • get_current_functionno sensitive capability
  • get_function_by_addressno sensitive capability
  • get_function_xrefsno sensitive capability
  • get_xrefs_fromno sensitive capability
  • get_xrefs_tono sensitive capability
  • list_classesno sensitive capability
  • list_data_itemsno sensitive capability
  • list_exportsno sensitive capability
  • list_functionsno sensitive capability
  • list_importsno sensitive capability
  • list_methodsno sensitive capability
  • list_namespacesno sensitive capability
  • list_segmentsno sensitive capability
  • list_stringsno sensitive capability
  • rename_datano sensitive capability
  • rename_functionno sensitive capability
  • rename_function_by_addressno sensitive capability
  • rename_variableno sensitive capability
  • search_functions_by_nameno sensitive capability
  • set_decompiler_commentno sensitive capability
  • set_disassembly_commentno sensitive capability
  • set_function_prototypeno sensitive capability
  • set_local_variable_typeno sensitive capability

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.1 latest A 100/100 0 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cylixlee-ghidra-mcp/badge.svg)](https://mcptrustchecker.com/registry/cylixlee-ghidra-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/cylixlee-ghidra-mcp"><img src="https://mcptrustchecker.com/registry/cylixlee-ghidra-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cylixlee-ghidra-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @cylixlee/ghidra-mcp --online

Use the free API → How scoring works

More in Developer Tools