henry-mcp
Related Servers
Alternatives to henry-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables an AI runtime to perform authorized static analysis of Android APKs over local MCP stdio, inspecting inventories, DEX/ELF headers and manifest details while decompiling with verified, checksum-pinned JADX and Apktool engines it can bootstrap itself. Reports results as evidence-backed observations, with literal text search, two-APK comparison and Markdown summaries, without ever executing the target APK.12MIT
- AlicenseAqualityCmaintenanceGives MCP clients such as Claude Code and OpenCode a static-analysis toolbox for binaries, executables, DLLs, shared objects, and web-app code, covering file identification and hashing, string extraction, PE/ELF/Mach-O/WASM parsing, disassembly, Ghidra decompilation, YARA scanning, and JavaScript deobfuscation. All inspection is read-only and never executes the target.16MIT
- AlicenseNot gradedqualityCmaintenanceEnables offline Android package analysis by loading APK, DEX, JAR, class, and XAPK files to inspect app metadata, manifests, classes, methods, resources, strings, and cross-references, and to export decompiled Java sources through CRUDE MCP-AQL tools.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents (and a matching CLI) to inspect native binaries, JavaScript/Electron apps, .NET assemblies, Go/Rust/WASM artifacts, EVM bytecode, SQLite databases, recorded crashes, and websites without source code, explaining how features work and returning the evidence and limitations behind each conclusion. Analysis runs locally, using optional Hopper, Ghidra, or IDA providers for native targets.371,123 npmMIT
- AlicenseNot gradedqualityCmaintenanceExposes 18 typed tools that drive real static-analysis engines (Ghidra, apktool, WABT, TShark, evmole, Rizin) over a single MCP endpoint to decompile binaries, audit APKs, scan EVM contracts, inspect WebAssembly, firmware, SQLite, and pcap data. Every call returns signed, verifiable evidence with an evidence_id, provider identity, SHA-256 artifact digest, and explicit limitations for security research, malware analysis, forensics, and CTF work.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to statically analyze Windows DLLs and query an evidence-grounded local agent for plain-English explanations, with claims tied to cited tool calls, addresses, and bytes.MIT
TDQS
Scored across 5 tools
The tools have largely distinct roles: inspect single files, compare a pair, predict pair failures, explain a finding, and reset state. The main possible confusion is between analyze_pair and predict_failure_scenarios, since both operate on app/module paths, but their descriptions clarify compatibility comparison versus scenario prediction.
All tools use a consistent henry_ prefix followed by snake_case verb-based names. The set follows a predictable naming convention throughout, with only henry_reset being a bare verb but still clear and consistent.
Five tools is well-scoped for a focused static analysis server. Each tool serves a clear purpose in the workflow, with no obvious bloat or missing cardinality issue.
The surface covers single-file inspection, pair analysis, failure prediction, finding explanation, and reset, which is most of the analyzer lifecycle. A minor gap is the lack of a list_findings or list_reports tool for discovering prior finding IDs without relying on earlier tool output.