hexvero
Related Servers
Alternatives to hexvero
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to inspect local application internals by analyzing JavaScript/Electron/ASAR and .NET artifacts, tracing dependencies, interfaces, and data flows, and preserving traceable evidence.14MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and CLI users to statically inspect any binary offline — identifying file type, architecture, imports, packing, embedded content and signatures — and to diff two files to see exactly what changed. It works on ELF, PE and Mach-O executables, firmware dumps and calibration files without ever running them, reporting observations and inferences with file offsets as evidence.76 npm1MIT
- AlicenseBqualityBmaintenanceEnables local, evidence-first triage of native binaries by extracting bounded symbols, strings, sections, call sites, gadget candidates, and mitigation signals as MCP tools for agent-guided manual review. It also provides metadata-only inspection for carriers such as archives, WebAssembly, firmware, and scripts without claiming verified vulnerabilities.125MIT

EVIDIQ Lineageofficial
AlicenseNot gradedqualityBmaintenanceDeterministic supply-chain provenance, SBOM/AI-BOM generation, and dependency risk analysis for npm and PyPI packages, with 14 security rules and verifiable reports.1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to scan Electron, JavaScript, Unity, Godot, .NET, and other builds for reverse-engineering exposures, explain findings, and generate apply-ready fix plans so agents can remediate high-risk issues before shipping. It supports read-only, offline analysis with secret masking and surface detection.430 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only, allowlisted-root scanning and deterministic comparison of binary and application artifacts, producing JSON/HTML evidence reports without executing the targets.MIT
TDQS
Scored across 16 tools
Most tools target distinct actions, but hexvero_provider_run overlaps heavily with hexvero_strings and hexvero_call_graph by including strings, callers, callees, and callgraph operations. The analyze/collection distinction is explained well, but the generic provider runner creates real selection ambiguity.
All tool names use a consistent hexvero_ prefix and lowercase snake_case, avoiding camelCase or mixed delimiters. The only minor inconsistency is semantic style: some names are verbs (open, close, analyze) while others are nouns (collection, bytes, unknowns).
Sixteen tools is slightly above the typical 3-15 range, but the domain is broad: binary/app analysis, extraction, comparison, policy checks, and recovery. Each tool appears to earn its place, though the general provider_run tool adds some surface area that dedicated tools already cover.
The surface covers target lifecycle, analysis, paged collection extraction, raw bytes/strings, export, comparison, policy checking, bundle/source recovery, and unknown tracking. Minor gaps remain, such as no clearly separate metadata/status retrieval beyond open/list and some overlap rather than missing core workflows.