{"id":"bytehow-ghidra-server","name":"ghidra-server","homepage":"https://hub.docker.com/r/bytehow/ghidra-server","repo_url":"https://hub.docker.com/r/bytehow/ghidra-server","category":"ai-ml","subcategories":[],"tags":["reverse-engineering","ghidra","binary-analysis","automation","api-server"],"what_it_does":"ghidra-server is a service for running Ghidra analysis headlessly and exposing it to other tools (e.g., to load binaries, run analysis workflows, and retrieve results) via an API interface.","use_cases":["Automating reverse-engineering workflows with Ghidra","Integrating Ghidra analysis into CI/CD or internal security tooling","Batch analysis of binaries for triage/research","Programmatic retrieval of decompiler/disassembly artifacts and analysis metadata"],"not_for":["Interactive, UI-based reverse engineering sessions","High-security deployments without careful network/auth controls","Environments where you cannot run headless analysis or manage the required runtime dependencies"],"best_when":"You need repeatable, programmatic Ghidra analysis at scale and can deploy/operate the server in your own infrastructure.","avoid_when":"You only need occasional manual analysis through the Ghidra GUI, or you cannot provide authentication/network hardening for an analysis-execution service.","alternatives":["Run Ghidra scripts directly (headless) via local automation","Ghidra + custom wrapper scripts (CLI headless mode)","Other reverse-engineering automation platforms","Commercial/alternative analysis services (depending on language/format support)"],"af_score":22.5,"security_score":19.5,"reliability_score":27.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:55:38.029282+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"Authentication/authorization mechanisms are not described in the provided data, so assume none/unknown; treat as requiring your own network-level protection if deployed."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted/open-source tooling implies costs are primarily infrastructure and operational effort; no pricing details were provided."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":22.5,"security_score":19.5,"reliability_score":27.5,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":25.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":20.0,"scope_granularity":20.0,"dependency_hygiene":30.0,"secret_handling":30.0,"security_notes":"As an analysis-execution service, it can be sensitive: treat all uploads as untrusted (potential parser/execution risks), restrict network exposure, require TLS, and use strong auth/authorization. No concrete security controls were provided in the supplied information.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":40.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["May require large binaries and significant compute/memory; timeouts or queueing can cause brittle automation.","Analysis runs are long-running; agents should expect asynchronous job patterns even if not documented here.","If authentication is absent/unclear, agents should not expose the service publicly."]}}