Ghidra MCP Server connects Ghidra, a software reverse-engineering tool for examining compiled programs, to AI tools through the Model Context Protocol (MCP), a standard way for applications to expose actions and data to language models. Reverse engineers use it to analyze binaries, automate batch work, and interact with Ghidra through graphical or headless operation. The catalogue entries provide instructions and MCP integration for working with the server.
Borrowing it
Nothing to install: this file belongs to bethington/ghidra-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bethington/ghidra-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/bethington/ghidra-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/bethington/ghidra-mcp/claude-md)<a href="https://agentmods.dev/instructions/bethington/ghidra-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bethington/ghidra-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/bethington/ghidra-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bethington/ghidra-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.09487 | $0.09487 |
| Opus 5 | $0.04744 | $0.04744 |
| Sonnet 5 | $0.01897 | $0.01897 |
| Haiku 4.5 | $0.00949 | $0.00949 |
Grade A, and why
ghidra-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ghidra MCP - Claude Code Guide
Overview
MCP server bridging Ghidra reverse engineering with AI tools. 253 MCP tools for binary analysis.
- Package:
com.xebyte| Version: 7.0.0 | Java: 21 LTS | Ghidra: 12.1.2
Boil the ocean
The marginal cost of completeness is near zero with AI. Do the whole thing. Do it right. Do it with tests. Do it with documentation. Do it so well that Ben is genuinely impressed — not politely satisfied, actually impressed. Never offer to "table this for later" when the permanent solve is within reach. Never leave a dangling thread when tying it off takes five more minutes. Never present a workaround when the real fix exists. The standard isn't "good enough" — it's "holy shit, that's done." Search before building. Test before shipping. Ship the complete thing. When Ben asks for something, the answer is the finished product, not a plan to build it. Time is not an excuse. Fatigue is not an excuse. Complexity is not an excuse. Boil the ocean.
Scope of "boil the ocean": code, analysis, and local work — never public or community actions. It means finish the engineering. It does NOT mean act autonomously on the community's behalf. See the next section.
Community interaction (read-only by default)
This is a public repo with real external contributors. Their issues, PRs, and commits are theirs, not yours to dispose of. Reading is always fine; every write below is the human maintainer's to do, and you may only draft text for Ben to review and post himself.
- Never edit, close, comment on, merge, or reopen another person's issue or PR without Ben's explicit, per-action go-ahead. Never edit anyone's issue/PR/comment text — that reads as tampering and is never acceptable.
- Draft / WIP / "do not merge" means hands off. Never cherry-pick, merge, or otherwise pull in a draft PR's work. Draft is the contributor's signal that it isn't ready; respect it.
- To use a contributor's work, merge their PR through the normal flow (which credits them) — never extract the commit around them or push it to
maindirectly. - Never post AI-generated text as if it were Ben's own analysis, and never post a claim about someone else's work without verifying it against the code first.
- When Ben asks for a reply to a contributor, produce a short draft for him to send in his own words — do not post it, and do not make it sound machine-generated.
- Exception:
dependabot[bot]PRs. These are the repo's own configured automation, not community contributions — no person's work is at stake. The agent may comment (e.g.@dependabot rebase/recreate) and merge these autonomously once CI is green, without per-action go-ahead. This exception is scoped to PRs whose author is literallydependabot[bot]; it does not extend to any human contributor, even one proposing a similar dependency bump. - A local
.claude/hook (block-community-github-writes.py) enforces a slice of this by denying write-shapedghcommands (checking PR authorship to carve out the dependabot exception above); treat that as a backstop, not the boundary. The boundary is this section.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago Changed · -2 lines · -65 tokens per session e0f248f1d5df
- 10d ago First seen · 316 lines · 9,552 tokens per session scan A 2ab6048df078
ghidra-mcp CLAUDE.md is an instructions file published in the GitHub repository bethington/ghidra-mcp (3,736 stars, last pushed 6d ago), licensed Apache-2.0. It adds 9,487 tokens to every session, about $0.0474 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.