App Analysis MCP
Related Servers
Alternatives to App Analysis MCP
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceEnables MCP clients to run evidence-first engineering investigations by gathering code, Git, log, and test evidence while avoiding fabricated root-cause claims.27-
- AlicenseAqualityCmaintenanceEnables compatible AI coding agents to inspect authorized software artifacts, analyze JavaScript/TypeScript and native binaries, optionally perform Ghidra decompilation, and produce verifiable evidence-linked technical reports.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to inspect local software structure, code, and runtime behavior through evidence-backed analysis, including sources, coverage, and limitations.1MIT
- AlicenseBqualityCmaintenanceEnables AI coding agents to perform evidence-based, read-only audits of supported software projects by exposing bounded project inventory and static-analysis findings for discovery, code review, integration tracing, security, and tests. Reports are returned as Markdown or JSON directly in the tool response, with no code executed or files written.817 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI clients to inspect backend systems through structured engineering tools including Git history, Winston logs, OpenAPI contracts, and sandboxed source code.2ISC
- AlicenseAqualityBmaintenanceEnables users to build and continuously refresh a code index of a repository, then query it to answer architecture, impact, tracing and log questions with verifiable evidence lines. Also checks Java, Kotlin and TypeScript/JavaScript names against real sources and classpaths, and supports commit review and Minecraft/JVM analysis directly from an agent session.51Apache 2.0
TDQS
Scored across 14 tools
Tools map cleanly onto a case lifecycle (status, create, triage, discover, call, inspect, run, read, record, report, close) with distinct purposes. The main overlap is workbench_analyze vs workbench_investigate_crash, since the crash tool bundles the same AST/linter/Semgrep/git primitives as analyze; workbench_call also acts as a generic escape hatch that could tempt use where run_check or analyze is intended. Descriptions largely resolve these boundaries.
All 14 tools share a workbench_ prefix and snake_case, with verbs mostly leading (create_case, run_check, record_finding, close_case). A few names are noun-only or ambiguous as verb/noun (workbench_status, workbench_report, workbench_triage), a minor deviation from the verb_noun pattern. Still highly predictable and scannable.
14 tools sit in the well-scoped 3-15 range and each covers a distinct stage of an investigation workflow rather than duplicating surface. Nothing appears redundant or filler, and the count reflects the genuine breadth of triage, evidence capture, execution, and reporting.
Full case lifecycle is covered: creation, triage, source inspection, check execution, evidence reading, finding recording, reporting, handoff, and close. Gaps are minor: there is no way to update or supersede a recorded finding, and no explicit resume/reopen operation for a closed case. Agents can work around these by creating new cases or records, but the surface is not entirely dead-end free.