Skip to main content
Glama
hlwhkw123123-sudo

FullStack Audit MCP

by hlwhkw123123-sudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to FullStack Audit MCP

No user-submitted related servers found.

    Related Servers

    • ChaiChai

      17lijunyi
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI clients to inspect local software structure, code, and runtime behavior through evidence-backed analysis, including sources, coverage, and limitations.
      MIT

    • codebase-doctor

      subhajitlucky
      A
      license
      A
      quality
      A
      maintenance
      Evidence-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.
      4
      2,726 npm
      MIT

    • RepoMind

      TaherFetoui
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      4 npm
      MIT

    • project-surface

      Richie11747
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query a repository's verified semantic model, including capabilities, ownership, contracts, constraints, impact, health, and verification status, without re-deriving project facts. It exposes read-only tools for inspecting, reasoning about, and verifying the provenance-tracked surface.
      2
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources