All servers · Markets & trading · Maps, location & weather · Utilities

io.github.RaYYeR220/regimen

io.github.RaYYeR220/regimen · v1.0.0

Measured by MCP Station

Description written by the publisher, not verified

Tells you whether a trading strategy's edge is distinguishable from luck.

Connect

claude mcp add --transport http regimen https://regimen-nu.vercel.app/mcp

{
  "mcpServers": {
    "regimen": {
      "url": "https://regimen-nu.vercel.app/mcp"
    }
  }
}

Tools as reported by the server

• 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, never changes.
• 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 Track Record Length — h
• 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 against spreads produ
• 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 strategy’s confidenc

Repository · Website · JSON · Text for agents · Registry updated 2026-09-19