No user-submitted related servers found.
Scored across 18 tools
Most tools target distinct operations, but there is real overlap: orangepro_start orchestrates much of what analyze_sources, find_test_gaps, and rtm do individually; orangepro_analyze_sources and orangepro_update_graph both (re)build the graph; orangepro_status and orangepro_graph_score both surface score/state; and prove vs prove_loop (explicitly a 'wrapper') can confuse selection. Descriptions do a good job disambiguating (e.g., changed_impact explicitly redirects baseline work to find_test_gaps), which keeps this from scoring lower.
All 18 tools use snake_case with a uniform 'orangepro_' prefix, which is strongly consistent. However, the naming convention is mixed: some are verb_noun (find_test_gaps, generate_tests, update_graph, record_run) while others are bare nouns or noun phrases (status, doctor, stats, rtm, graph_score, changed_impact), so the pattern is not predictably verb-first throughout.
18 tools is on the heavy side but justified by a genuinely broad domain (graph analysis, gap detection, test generation, dynamic proof, AI lanes, reporting, export). Most tools earn their place, though a few (start vs analyze_sources, prove vs prove_loop, status vs graph_score) could arguably be consolidated, pushing it slightly past the ideal 3-15 range.
Coverage is strong across the full lifecycle: setup/analysis (start, analyze_sources, update_graph, status, doctor, graph_score), gaps (find_test_gaps), generation (generate_tests, explain_test), proof (prove, prove_loop, record_run), ledger/reporting (stats, rtm), AI lanes (ai_links, ai_flows), diff/PR (changed_impact), and export (export_evidence_pack). Minor gaps exist—no config/privacy settings tool despite status reporting privacy settings, and no standalone report-regeneration or ledger-cleanup/reset—but these are workaroundable.
