Regimen
by regimen-nu.vercel.app in Markets & finance
Tells you whether a trading strategy's edge is distinguishable from luck.
https://regimen-nu.vercel.app/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 290 ms typical, 290 ms slowest 5%
- Last check
- 3 h ago
- Next check
- in 2 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"regimen": {
"type": "http",
"url": "https://regimen-nu.vercel.app/mcp"
}
}
}4 tools
- regimen_describe_factors
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, nev
- regimen_evaluate_track_record
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 Tra
- regimen_regime_map
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 a
- regimen_self_attack
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
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 3 h ago | Passed | 200 | 290 ms |
| 12 h ago | Passed | 200 | 1.2 s |