Skip to main content
Glama
rodlunt

engineering-audit

by rodlunt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to engineering-audit

No user-submitted related servers found.

    Related Servers

    • repo-contract

      dager23
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enforces repository governance rules for AI coding agents, providing tools to validate plans, diffs, and scan for architectural and safety violations.
      1
      MIT

    • code-guardian

      xueca
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides code quality checks for AI coding assistants, including file size limits, ESLint, architecture compliance, anti-pattern scanning, and comment compliance.
      7 npm
      MIT

    • code-review-mcp

      AlanNiew
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides local code quality analysis for AI coding assistants, supporting file analysis, git diff review, and full project scanning with quality scoring.
      4
      3
      MIT

    • sdlc-integrity-mcp

      AsobaCloud
      A
      license
      A
      quality
      A
      maintenance
      MCP server that provides audit and safety-check tools for enterprise SDLC code integrity, enabling AI agents to scan workspaces for lifecycle gaps, mock-theater tests, DRY violations, and language-specific issues in shell, JavaScript/HTML, and Python.
      4
      6 npm
      MIT

    • devflow-mcp

      boranesn
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that provides AI assistants with comprehensive GitHub developer tooling including PR analysis, code review, changelog generation, dependency auditing, commit summarization, and refactoring suggestions.
      10 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the audit workflow: configuration, run lifecycle, domain metadata, rule text, result recording, progress reporting, report rendering, issue filing, and feedback. Even closely related pairs like list_domains/get_domain and start_config/get_config are cleanly separated by action and state. No two tools plausibly do the same job.

    Naming Consistency4/5

    Nine of ten tools follow a clear verb_noun snake_case pattern: begin_run, list_domains, get_domain, record_domain_result, render_report, file_issues, submit_feedback, start_config, get_config. The outlier is run_status, which reads as a noun phrase rather than an imperative verb+object form. It is still stylistically consistent and readable, so this is only a minor deviation.

    Tool Count5/5

    Ten tools map cleanly onto the full audit lifecycle without redundancy or bloat. Each tool earns its place, covering configuration, run start/resume/status, domain and rule inspection, result recording, report rendering, issue filing, and feedback submission. The scope is well matched to the server's purpose.

    Completeness4/5

    The tool surface covers the core audit lifecycle well: configuration, run management, domain discovery, rule text retrieval, result recording, rendering, issue filing, and feedback. The main gap is that previously recorded findings are only summarized by run_status or surfaced indirectly via file_issues and render_report; there is no direct tool to reread detailed recorded results after resuming a run. This is a workable omission rather than a dead end.

    Maintenance

    ActivityNo data
    ResponsivenessResponsive

    Resources