file-reviewer
Related Servers
Alternatives to file-reviewer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityDmaintenanceEnables 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 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables code auditing, scanning for committed secrets and vulnerable dependencies, and generating self-review checklists, with optional paid audit pricing.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityAmaintenanceEnables MCP clients to run deterministic AST safety audits, secret scanning, and sandboxed test execution on codebases, with human approval required before any remediation action.5MIT
TDQS
Scored across 18 tools
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.
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.
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.
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.