io.github.RaYYeR220/regimen

Est-ce que io.github.RaYYeR220/regimen est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.RaYYeR220/regimen » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• regimen_describe_factors≈ 304 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "regimen_describe_factors", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "factors": []}}

• regimen_evaluate_track_record≈ 1434 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • detail · string · optionnel · concise | full
    concise returns the verdict, the headline statistics and the reasoning — enough to answer a user. full adds every bucket, every dropped point and the complete provenance list, and is much larger.
  • selector · object · requis
    Which track record to analyse.
  • confidence · number · optionnel
  • trialSharpes · array · optionnel
    Per-period Sharpe ratios of other configurations tried for this strategy. Supplying them enables the Deflated Sharpe Ratio, which discounts the headline for how many variants were tested before this one was reported.
  • benchmarkSharpe · number · optionnel
    Per-period Sharpe the record must beat. 0 asks only whether there is any edge at all.

  Exemple d'appel

  {"name": "regimen_evaluate_track_record", "arguments": {"selector": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"full": "texte", "label": "texte", "notes": [], "verdict": "texte", "headline": "texte", "sourceId": "texte", "reasoning": [], "usableReturns": 1, "deflatedSharpe": 1, "sharpePerPeriod": 1, "sharpeAnnualised": 1, "probabilisticSharpe": 1}}

• regimen_regime_map≈ 1260 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • detail · string · optionnel · concise | full
    concise returns the verdict, the headline statistics and the reasoning — enough to answer a user. full adds every bucket, every dropped point and the complete provenance list, and is much larger.
  • maxDates · integer · optionnel
    How many of the most recent dates to read conditions for, bounded by the upstream rate limit.
  • selector · object · requis
    Which track record to analyse.
  • minSample · integer · optionnel
    Buckets below this many observations are returned but flagged unusable.

  Exemple d'appel

  {"name": "regimen_regime_map", "arguments": {"selector": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"full": "texte", "label": "texte", "factors": [], "warnings": [], "minSample": 1, "datesCovered": 1}}

• regimen_self_attack≈ 1039 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • selector · object · requis
    Which track record to analyse.
  • simulations · integer · optionnel

  Exemple d'appel

  {"name": "regimen_self_attack", "arguments": {"selector": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"label": "texte", "notes": [], "verdict": "texte", "controls": [], "nullDistribution": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://regimen-nu.vercel.app/mcp