vesper
Related Servers
Alternatives to vesper
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for iOS reverse engineering, enabling static analysis of IPA/Mach-O binaries and dynamic instrumentation via Frida for tasks like IAP interception and FairPlay decryption.323MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform local iOS reverse engineering through MCP by importing IPA files, querying Mach-O and Ghidra analysis for functions, references, calls, and approximate pseudocode, and saving evidence-backed findings. It supports investigation cases and exports HTML, Markdown, or JSON reports with provenance.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that enables agents to reverse engineer applications, from high-level behavior down to native binaries, using tools like Hopper and Ghidra.351,882 npm456,332MIT
- FlicenseBqualityDmaintenanceMCP server for iOS Frida exploration enabling app control, UI interaction, and media import via spawn sessions on jailbroken devices.5396 npm2-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to reverse-engineer binary files — hex viewing, disassembly, function/call-graph recovery, syscall and RTTI naming, string/xref search, and symbol export for Ghidra and IDA — across Switch NSO/NRO/NSP and many other formats. Tool output is persisted as annotations so analysis carries across sessions.MIT
- AlicenseAqualityAmaintenanceEnables Android APK reverse engineering and Flutter runtime injection through a six-step pipeline of decompile, analyze, synthesize, inject, patch, and repackage. Provides MCP tools for authorized security research and penetration testing.943 npm5MIT
TDQS
Scored across 19 tools
Most tools map cleanly to a resource+action, but several boundaries blur: ui_snapshot and ui_capture both return bounded UIKit summaries (capture also returns a snapshot_id), frida_detach vs frida_unhook differ only by scope, and platform_tool exposes objc_get_ivars/ui_inspect_view/device_* primitives that duplicate top-level tools. The verbose descriptions mitigate this but an agent must read carefully to pick the right one.
There is a predictable domain-prefix convention (device_, frida_, objc_, ui_, app_, debug_, job_, server_, platform_), all in snake_case. Minor deviations exist within groups (verb-first frida_get_events/frida_trace_method vs. noun-first device_info/objc_dump/ui_snapshot), but the scheme remains readable and guessable.
Nineteen tools is on the heavy side, but the domain (iOS dynamic analysis over SSH+Frida) genuinely needs distinct workflows for device discovery, ObjC introspection, UI automation, logging, debugging, decryption and job control. Some consolidation is possible (ui_snapshot/ui_capture, detach/unhook), but no tool looks wholly gratuitous.
Coverage is strong for the inspection/RE lifecycle (discover, attach, query, trace, dump, UI, logs, debug, decrypt) plus a platform_tool escape hatch for ida_*/tweak_* primitives. However, obvious gaps remain in the explicit surface: no file transfer (pull/push), no process list/launch/kill, and no shell execution, which agents will hit in real iOS workflows.