regimen
Server Details
Tells you whether a trading strategy's edge is distinguishable from luck.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- RaYYeR220/regimen
- GitHub Stars
- 0
- Server Listing
- regimen
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: listing available factors, testing whether performance beats luck, decomposing returns by regime, and validating the engine itself. There is no meaningful overlap or ambiguity about which tool to call.
All tools share the regimen_ prefix and use snake_case, making them easy to group. The pattern is mostly verb_noun, but regime_map and self_attack are noun-first, which is a minor deviation.
Four tools is appropriate for this focused server: each tool earns its place and covers a distinct stage of the validation workflow. It is neither bloated nor too thin for its stated purpose.
The tool surface covers the full skeptical analysis pipeline: understand the factors, evaluate the headline claim, locate the edge by regime, and verify that the engine itself is not fooled. There are no obvious dead ends or missing operations for this domain.
Available Tools
4 toolsregimen_describe_factorsDescribe regime factorsARead-onlyIdempotentInspect
List the market-condition factors Regimen slices performance by, with units, the upstream operation each is read from, and how it is bucketed. Call this when you need to know which factor keys exist or how to explain a bucket to a user. Takes no arguments, reaches no network, never changes.
Inputs: no named parameters. Returns: note, factors
regimen_evaluate_track_recordEvaluate a track recordARead-onlyInspect
Answer whether a trading strategy’s measured performance is distinguishable from luck. Returns the Probabilistic Sharpe Ratio (the probability the true Sharpe beats a benchmark, corrected for sample length, skew and fat tails), a bootstrap confidence interval, and the Minimum Track Record Length — how long the record would have to run before the claim could be made at all. Use this whenever someone quotes a Sharpe ratio, a win rate or a return and you need to know whether the number means anything. It will frequently say the evidence is too thin; that is the intended answer, not a failure.
Inputs: selector (required), detail, confidence, trialSharpes, +1 more. Returns: full, label, notes, verdict, +12 more
regimen_regime_mapMap performance to market regimesARead-onlyInspect
Break a strategy’s returns down by the market conditions that held on each date — volatility, funding, open interest, positioning, sentiment, trend state — and report performance per bucket. Each factor also gets a permutation test: the observed best-to-worst spread is compared against spreads produced by randomly reshuffling the regime labels, so a flattering subset cannot pass itself off as a regime effect. Use this after regimen_evaluate_track_record when you need to know WHERE an edge comes from, or whether it is a bet on conditions that could end.
Inputs: selector (required), detail, maxDates, minSample. Returns: full, label, factors, warnings, +2 more
regimen_self_attackAttack the verdictARead-onlyInspect
Run Regimen’s own analysis against controls whose answer is known in advance: the strategy’s returns with the edge mathematically removed, and a simulated population of strategies with no edge at all. Returns whether the engine correctly found nothing in them, and where the real strategy’s confidence sits among pure-luck strategies of the same length and volatility. Use this when a user is entitled to ask why they should believe the verdict, or before quoting a result as evidence.
Inputs: selector (required), simulations. Returns: label, notes, verdict, controls, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Is a trading strategy's track record luck? Free luck check, plus what a full strategy audit checks.
Grade a track record before risking capital: REAL_EDGE/REGIME_LUCK/NEGATIVE_EV. Fail-closed.
Checks crypto trading claims on real data: leverage, drawdown, stop-loss, seasonality, luck.
Is a backtest's Sharpe ratio real or luck? Deflated Sharpe Ratio check with green/yellow/red.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables statistical validation of whether a trading backtest’s edge is real using bootstrap-resampling and reshuffling Monte Carlo methods, including confidence intervals, drawdown-path percentiles, expected value calculations, and prop-firm challenge pass-probability simulation. It also compares multiple win-rate/risk-reward geometries by simulated pass rate.MIT
- AlicenseNot gradedqualityDmaintenanceChecks whether a trading backtest survives its own statistics: deflated Sharpe, multiple-testing correction against a best-of-N-noise benchmark, minimum track record length, and fill realism. Takes no market data and no API keys, and cannot recommend a trade — it only reports that a result is weaker than claimed or not yet provable.MIT
- AlicenseNot gradedqualityBmaintenanceGrades prediction market trade logs to determine if a strategy has a statistically significant, fee-adjusted edge using out-of-sample holdout, returning a signed verdict.MIT
- AlicenseNot gradedqualityDmaintenanceEnables quant traders and researchers to test whether a strategy's edge is genuine or an artifact of testing many variants, via Probability of Backtest Overfitting, Deflated Sharpe Ratio, Minimum Backtest Length, and purged/embargoed cross-validation splits.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.