No user-submitted related servers found.
Scored across 19 tools
The validate_* family shares a theme (multiple-testing/luck), but descriptions clearly separate each method and even cross-reference the right alternative (e.g. 'for the probability the Sharpe is real, use validate_deflated_sharpe'). The main soft spot is the overlap between the umbrella audit_backtest and its component validators, which an agent must reason about, but the docs reduce this to occasional hesitation rather than true ambiguity.
A strong verb_noun convention dominates (validate_*, check_*, get_key, verify_receipt, backtest_strategy, stress_test), with only minor deviations like the noun-style service_status. Overall readable and predictable, not chaotic.
19 tools is slightly on the heavy side, but each maps to a distinct statistical method or workflow step (validation, key handling, receipts, backtesting, diagnostics), so most earn their place. It sits just above the ideal range but is defensible given the specialized domain.
The surface covers the full strategy-validation lifecycle: key/status management, individual and bundled validation methods, offline receipt verification, backtesting, series summarization, stress testing, feasibility, leakage, and placebo testing. No obvious gaps or dead ends for the stated purpose.