ghidra-mcp (bethington/ghidra-mcp) is an MCP server listed on the M8ven Trust Index. It scores 75 out of 100, grade B. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Limited view
75/100
1 month ago

ghidra-mcp

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.

→ bethington/ghidra-mcp· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Java is partially covered.

How we verified

Code VerifiedSandbox Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

bethington

Source: Glama · also listed on github_topic, github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GlamaGitHubGitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: FUN_DOC_DASHBOARD_TOKEN, ANTHROPIC_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGHIDRA_MCP_URL
configTOOLS_SETUP_BACKENDbuild Build the plugin JAR and extension ZIP via Maven (or Gradle when =gradle).
configXDG_CONFIG_HOME
configGHIDRA_DEBUGGER_PYTHON
configCOMSPEC
configGRADLE_HOME
configM2_HOME
configFUNDOC_VC6_SOURCE
configFUNDOC_VS7_SOURCE
configSCYLLAHIDE_DIR
configSCYLLAHIDE_AUTO_INJECT
configFUNDOC_D2MOO_REPO
configD2DBG_MCP_URL
configGHIDRA_PROGRAM
configV1_MAX_VECTORS
configV1_MODEL
configFUNDOC_GHIDRA_PROGRAM
configAI_PROVIDER
configFUN_DOC_PROJECT_FOLDER
configGHIDRA_URL
configGHIDRA_SERVER_URL
configFUNDOC_OPEND2_REPO
configFUNDOC_CONSOLE_MARKERS
configSystemRoot
configFUNDOC_CONSOLE_CLEANUP
configCRT_IDENTIFY_LIBS
configFUNDOC_EVENT_LOG
configFUNDOC_GHIDRA_POLL_SEC
configFUNDOC_GHIDRA_AUTO_LAUNCH
configFUNDOC_GHIDRA_AUTO_LAUNCH_AFTER
configFUNDOC_GHIDRA_LAUNCH_COOLDOWN
configFUNDOC_GHIDRA_LAUNCH_BURST
configFUNDOC_GHIDRA_LAUNCH_MAX_COOLDOWN
configFUN_DOC_LOG_MAX_BYTES
configFUN_DOC_LOG_BACKUPS
configFUNDOC_NOTIFY
configFUNDOC_NOTIFY_MIN_REPEAT
configFUNDOC_LIVE_PROVE
configD2MOO_LAUNCH_BAT
configD2MOO_PROVE_CHARACTER
configFUNDOC_ORACLE_POLL_SEC
configFUNDOC_ORACLE_AUTO_RECOVER
configFUNDOC_ORACLE_AUTO_RECOVER_AFTER
configFUNDOC_ORACLE_AUTO_RECOVER_COOLDOWN
configFUNDOC_ORACLE_AUTO_RECOVER_MAX
configFUNDOC_ORACLE_AUTO_RECOVER_MAX_COOLDOWN
configFUNDOC_ORACLE_IDLE_AFTER
configFUNDOC_ORACLE_ENTER_GAME_COOLDOWN
configFUNDOC_ORACLE_FROZEN_AFTER
configFUNDOC_ORACLE_PRESENT_MIN_SEC
configFUNDOC_SHADOW_PROMOTE
configFUNDOC_PROVIDER_BUILD_LOCK_TIMEOUT
configFUNDOC_INFLIGHT_TTL_SEC
configFUNDOC_CMAKE_GENERATOR
configFUNDOC_CMAKE_ARCH
configFUNDOC_MUTATOR_LEAF
configFUNDOC_D2MOO_BUILD_TREE
configFUNDOC_HEARTBEAT_INTERVAL_SEC
configFUNDOC_STALL_KILL_THRESHOLD_SEC
configFUNDOC_STALL_ACTIVITY_GRACE_SEC
configFUNDOC_STALL_KILL_HARD_CAP_SEC
configFUN_DOC_DASHBOARD_ORIGINS
🔐 secretFUN_DOC_DASHBOARD_TOKEN
configFUNDOC_VC6_ROOT
configFUNDOC_VS7_ROOT
configFUNDOC_BENCHMARK_PROGRAM
configFUNDOC_BENCHMARK_NO_LLM
🔐 secretANTHROPIC_API_KEY
configFUNDOC_BENCHMARK_ALLOW_SHARED
configFUN_DOC_DB_URL
configFUNDOC_DRAFT_ONLY
configFUNDOC_DOC_TAGS
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

8/8 tools missing one or more hints — list_instances (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); connect_instance (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_tool_groups (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

6/8 tool handlers declare input schemas (75%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 1/8 tool handlers wrap calls in try/catch (13%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/bethington/ghidra-mcp)](https://m8ven.ai/mcp/bethington/ghidra-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 0e5f0a410c652cbb90aa30a953ce69b55a5d26a7
code hash: 97be83d1b3836bc06c4bef3c619967427e4edff1a186549cee5c10729b75ef82
verified: 8/6/2026, 5:32:34 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client