No user-submitted related servers found.
Scored across 6 tools
Each tool has a clearly distinct purpose, and descriptions explicitly cross-reference alternatives (e.g. 'For a repository health check that is not about one change, use repopilot_scan instead'). The three explain tools are cleanly separated by input type: file, finding_id, and signal_id.
All tools share the repopilot_ prefix and mostly follow a verb_noun pattern (review_change, explain_file, explain_finding, explain_review_signal). Minor deviations: 'scan' and 'context' are single tokens without an explicit object, though still readable.
Six tools is well-scoped for a focused code-review/audit server, with three core operations (review_change, scan, context) plus three targeted explainers. Every tool earns its place.
The surface covers the full lifecycle of the domain: producing a review, a scan, a brief, and explaining findings, signals, and file treatment. Minor gap: no explicit tool to list or manage prior session handles beyond passing analysis_handle, but core workflows are covered.