FullStack Audit MCP
Related Servers
Alternatives to FullStack Audit MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to inspect local software structure, code, and runtime behavior through evidence-backed analysis, including sources, coverage, and limitations.1MIT
- 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
- AlicenseAqualityBmaintenanceEvidence-backed, read-only codebase diagnostics for coding agents: secrets, dependency, RLS, and source-impact audits with a verify loop and PR review verdicts. Never writes files or uses the network by default.7114 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to inspect local and remote repositories through sandboxed tools that surface project overviews, structure, dependency audits, Git churn hotspots, and a heuristic health score. It also supports safe GitHub issue searching and creation with built-in duplicate preflight checks, while blocking sensitive files, binary content, and path traversal attacks.22 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scan code for security and quality issues and receive machine-readable reports with suggested fixes and verification criteria.83 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to run read-only repository health checks for leaked secrets, code quality, and project structure. Exposes tools to scan repositories, retrieve Markdown or JSON reports, and filter findings by severity, rule, or path while confining access to allowed roots.1MIT
TDQS
Scored across 8 tools
Each tool targets a distinct audit phase: discovery, generic heuristics, frontend/backend/security/test reviews, integration tracing, and reporting. The only soft overlap is analyze_code versus the domain-specific reviews (review_security, review_frontend/backend), which all run static heuristics over source, so an agent could be unsure when to use the generic analyzer versus a targeted review. Descriptions mostly clarify these boundaries.
All eight tools follow a clean verb_noun snake_case pattern (scan_project, analyze_code, review_frontend, generate_audit_report, etc.). The verb prefixes (scan/analyze/review/trace/generate) map predictably to the action performed.
Eight tools is well-scoped for a static audit server, with each tool covering a coherent slice of the pipeline from discovery through reporting. No tool feels redundant or like filler.
The surface covers the full audit lifecycle: discovery, code analysis, frontend/backend/security/test review, integration tracing, and reporting. Minor gaps exist, such as no dependency/package vulnerability audit and no remediation guidance, but these are reasonable for a read-only static analyzer.