Skip to main content
Glama
wenshuo0114

file-reviewer

by wenshuo0114

Related Servers

Alternatives to file-reviewer

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only GitHub repository inspection and deterministic intelligence through MCP tools for repository metadata, file contents, issue triage, pull-request risk signals, and GitHub Actions failure investigation.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive security scanning of code repositories to detect secrets, vulnerabilities, dependency issues, and configuration problems. Provides real-time security checks and best practice recommendations to help developers identify and prevent security issues.
      8 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to run deterministic, read-only local repository audits for risky GitHub workflows, undocumented environment variables, possible credentials, and conflicting dependency configuration, returning structured findings without sending source code to a service.
      63 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables code auditing, scanning for committed secrets and vulnerable dependencies, and generating self-review checklists, with optional paid audit pricing.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely inspect a local repository's code and metadata while blocking private data from leaving the machine, providing read-only tools for search, change tracking, and integrity verification.
      MIT

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    The tool set is cleanly separated into review_*, report_*, review_queue_*, and rollback_* families, and within review_* the scanning, secrets, external paths, user-level configs, metadata, and single-file read functions target different objects. Even actions like report_write_decision and report_external_choice are distinguishable by the description: one records a finding decision, the other records an external-reference choice.

    Naming Consistency4/5

    The namespace-prefix pattern (review_/report_/rollback_/review_queue_) is consistent and predictable, but suffixes mix target nouns like file_metadata and secrets_inventory with imperative verbs like open, read, set_header, and write_fix. This is a minor style inconsistency rather than a functional confusion.

    Tool Count4/5

    18 tools is above the typical 3-15 range, but each tool maps to a distinct step in an unusually complete review workflow: opening repos, scanning files/configs, queuing external paths, writing report entries, and managing rollbacks. The count feels slightly heavy for a single server, but no tool is redundant.

    Completeness4/5

    The tool surface covers the review lifecycle well, including entering repos, scanning files and configs, logging decisions and fixes, queuing external paths, and rollback safety. Minor gaps remain: there is no tool to read or finalize the full report from within the server, and rollback_create implies file edits without a matching edit tool, but agents can work around these using report paths and external file tooling.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues