updated 2026-10-13 04:10 UTC

Ghidra MCP

Repository

Ghidra MCP Server — 200+ MCP tools for AI-powered reverse engineering. GUI plugin + headless server, lazy tool loading, convention enforcement, batch operations, Ghidra Server integration, and Docker deployment.

MCP Servers Java Listed Apache-2.0

Is Ghidra MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.8 / 10
Provenance None
Signed commits 32%
Last push 4d ago
Compare Ghidra MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Ghidra MCP scores 64.6/100 (Grade C), ranked #517 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.8/10; 32% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ghidra MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Ghidra MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/bethington/ghidra-mcp, Apache-2.0, last pushed 2026-10-09. 32% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.8/10 (scanned Oct 12, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies7
    All 18 Scorecard checks
    Binary-Artifacts 7
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 7
    SAST 7
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages None

    No registry package. Ghidra MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Ghidra MCP.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Ghidra MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Ghidra MCP compares in MCP Servers

  1. #290 Yuque MCP Server 64.8 +0.2
  2. #291 Screaming Frog SEO Spider MCP Server 64.8 +0.2
  3. #292 Ghidra MCP 64.6 this agent
  4. #293 Anythingmcp 64.6 ±0
  5. #294 Better Telegram MCP 64.6 ±0

Bars show each HVTrust score; the tick marks Ghidra MCP’s 64.6.

Where the 64.6 comes from

HVTrust dimensions vs the MCP Servers average

64.6 / 100 · 100.0% confidence

Ghidra MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.1 / 25
in line with avg 10.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
14.3 / 17
2.1 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
7.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.0 / 20
1.6 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-11
Rank Moved
Rank rose 71 spots (#579 → #508)
2026-10-10
Rank Moved
Rank dropped 36 spots (#543 → #579)
2026-10-08
Rank Moved
Rank dropped 35 spots (#511 → #546)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Ghidra MCP View MCP Servers Report missing data
83.7
Activity sub-score · out of 100
#292
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-13 04:10 UTC · Repo last pushed 4 days ago

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
5.5k
Forks
305
Last Push
2026-10-09
4 days ago
Commits (4 wk)
139
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
16
Rank Change
▼4
was #513

Analysis

Activity Inputs

83.7 / 100
StarsRepository reach
22.5 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.6 / 20

Common questions about Ghidra MCP

Ghidra MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Ghidra MCP publish package provenance?
No published build provenance is currently detected for Ghidra MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ghidra MCP have an OpenSSF Scorecard?
Ghidra MCP has an OpenSSF Scorecard score of 6.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Ghidra MCP actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Ghidra MCP use?
Ghidra MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ghidra MCP's commits signed?
32% of the last 100 commits to Ghidra MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Ghidra MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Ghidra MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

Maintain Ghidra MCP?

For maintainers

HVTrust scores Ghidra MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 35Score 2HVTrust 2Grade 2Surface 1Surface 1
2026-10-11
Rank Moved
Rank rose 71 spots (#579 → #508)
2026-10-10
Rank Moved
Rank dropped 36 spots (#543 → #579)
2026-10-08
Rank Moved
Rank dropped 35 spots (#511 → #546)
2026-10-07
Rank Moved
Rank dropped 16 spots (#495 → #511)
2026-10-06
Rank Moved
Rank rose 15 spots (#510 → #495)
2026-10-05
Rank Moved
Rank rose 14 spots (#524 → #510)
2026-09-30
Grade Changed
Trust grade B → C
2026-09-30
Rank Moved
Rank dropped 45 spots (#473 → #518)
2026-09-28
Rank Moved
Rank dropped 29 spots (#449 → #478)
2026-09-24
Rank Moved
Rank rose 19 spots (#465 → #446)
2026-09-23
Rank Moved
Rank dropped 284 spots (#181 → #465)
2026-09-21
Rank Moved
Rank rose 272 spots (#456 → #184)
2026-09-19
Grade Changed
Trust grade C → B
2026-09-19
Rank Moved
Rank rose 240 spots (#697 → #457)
2026-09-19
HVTrust Changed
HVTrust up 7.9pts (57.4 → 65.3)
2026-09-19
Activity Score Changed
Activity score up 10pts (70 → 80)
2026-09-11
Rank Moved
Rank rose 10 spots (#698 → #688)
2026-09-09
Rank Moved
Rank dropped 132 spots (#571 → #703)
2026-09-09
HVTrust Changed
HVTrust down 4.1pts (60.6 → 56.5)
2026-09-09
Activity Score Changed
Activity score down 7pts (74 → 67)
2026-09-08
Rank Moved
Rank dropped 26 spots (#545 → #571)
2026-09-07
Rank Moved
Rank dropped 44 spots (#501 → #545)
2026-09-06
Rank Moved
Rank dropped 12 spots (#489 → #501)
2026-09-05
Rank Moved
Rank dropped 96 spots (#393 → #489)
2026-09-03
Rank Moved
Rank dropped 31 spots (#357 → #388)
2026-08-31
Rank Moved
Rank dropped 25 spots (#315 → #340)
2026-08-30
Rank Moved
Rank rose 12 spots (#327 → #315)
2026-08-27
Rank Moved
Rank dropped 10 spots (#317 → #327)
2026-08-26
Rank Moved
Rank dropped 25 spots (#292 → #317)
2026-08-24
Rank Moved
Rank dropped 16 spots (#273 → #289)
2026-08-22
Rank Moved
Rank rose 12 spots (#289 → #277)
2026-08-19
Rank Moved
Rank dropped 13 spots (#280 → #293)
2026-08-17
Rank Moved
Rank rose 11 spots (#290 → #279)
2026-08-13
Rank Moved
Rank dropped 21 spots (#265 → #286)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-08-10
Rank Moved
Rank dropped 16 spots (#290 → #306)
2026-08-08
Rank Moved
Rank dropped 68 spots (#215 → #283)
2026-08-04
Rank Moved
Rank dropped 11 spots (#188 → #199)
2026-08-03
Rank Moved
Rank dropped 31 spots (#157 → #188)
2026-07-24
Rank Moved
Rank rose 13 spots (#171 → #158)
2026-07-21
Rank Moved
Rank rose 28 spots (#199 → #171)
2026-07-20
Rank Moved
Rank dropped 30 spots (#169 → #199)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.6 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/ghidra-mcp.svg)](https://hvtracker.net/agents/ghidra-mcp)
HTML:
<a href="https://hvtracker.net/agents/ghidra-mcp"><img src="https://hvtracker.net/badge/ghidra-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON