🔍 Ghidra MCP Server

Created By
Bamimore-Tomia year ago
Ghidra MCP server that extracts decompiled binary context and exposes it to LLMs via Model Context Protocol.
Overview

What is Ghidra MCP Server?

Ghidra MCP Server is a tool that allows users to utilize Ghidra in headless mode to extract detailed binary analysis data and expose it to large language models (LLMs) via the Model Context Protocol (MCP).

How to use Ghidra MCP Server?

To use Ghidra MCP Server, install the required software, set up the project, and run the server using the MCP CLI. You can then interact with the server to analyze binaries and retrieve information.

Key features of Ghidra MCP Server?

  • Decompiles binaries using Ghidra in headless mode.
  • Extracts function pseudocode, data structures, and function definitions.
  • Outputs analysis results to a JSON file.
  • Provides various tools for interacting with the extracted data via MCP.

Use cases of Ghidra MCP Server?

  1. Analyzing malware by extracting and understanding its binary structure.
  2. Assisting in reverse engineering software for security assessments.
  3. Enabling automated analysis of binaries for research purposes.

FAQ from Ghidra MCP Server?

  • What are the system requirements for Ghidra MCP Server?

Requires macOS, Python 3.10+, Ghidra 11.3.1+, and Java 21.

  • Can I use Ghidra MCP Server on Windows?

Currently, it is tested on macOS only.

  • How do I install the MCP client?

You can install it via pip with the command pip install mcp.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Bamimore-Tomi
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago