No user-submitted related servers found.
Scored across 29 tools
Most tools target a distinct resource+action (compose_graph vs backtest_graph vs backtest_status, export_paper vs export_atlas vs export_tearsheet, the v9_* scanner family vs the backtest_* graph family). A few clusters overlap thematically, notably the evaluation tools (red_flag_check, adversarial_check, reality_check_profiles, diagnostics_catalog/explain) and the app-control trio (live_state, set_live_state, pilot_app), but descriptions explicitly cross-reference 'use X instead', resolving most confusion.
Everything is snake_case with a predictable, readable style and useful subsystem prefixes (backtest_, export_, diagnostic_, v9_). The main deviation is that some tools are verb_noun (compose_graph, export_paper, red_flag_check) while others are noun-only (app_info, data_sources, node_catalog, live_state), so the verb pattern isn't fully uniform.
29 tools is on the heavy side and includes clear bloat (set_live_state is explicitly legacy, run_smoke_tests is dev-only), which everyone pays the surface-area cost for. Still, the server spans genuinely different subsystems—graph backtesting, a separate batch scanner, portfolio combination, report export, diagnostics, and app piloting—so the count is defensible rather than gratuitous.
The research lifecycle is well covered: discover nodes/registries/data sources, compose and run graphs, poll status, judge results (red_flag_check, adversarial_check, portfolio_combine), and export papers/tearsheets, plus the parallel v9 scanner surface and app/diagnostics introspection. Minor gaps exist—e.g. no tool to enumerate the day's session run registry directly, and inspection of graph runs depends on a run_id from a prior call—but these are workable.
