# io.github.RaYYeR220/regimen (remote · regimen-nu.vercel.app)

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

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `regimen-nu.vercel.app`: 76/100 (this document), [markdown](https://verifymcp.io/servers/rayyer220-regimen/regimen-nu.md), [page](https://verifymcp.io/servers/rayyer220-regimen/regimen-nu)

## Channel facts

- Endpoint: `https://regimen-nu.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1140 tokens (~81/item across 14 items; 4 tools + 10 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.RaYYeR220/regimen MCP server?

io.github.RaYYeR220/regimen is a hosted endpoint at https://regimen-nu.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http rayyer220-regimen 'https://regimen-nu.vercel.app/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "rayyer220-regimen": {
      "type": "http",
      "url": "https://regimen-nu.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.rayyer220-regimen]
url = "https://regimen-nu.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rayyer220-regimen": {
      "type": "remote",
      "url": "https://regimen-nu.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rayyer220-regimen --url 'https://regimen-nu.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rayyer220-regimen:
    url: "https://regimen-nu.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "rayyer220-regimen": {
      "Transport": "http",
      "Url": "https://regimen-nu.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add rayyer220-regimen -t streamable-http -u 'https://regimen-nu.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "rayyer220-regimen": {
      "type": "http",
      "url": "https://regimen-nu.vercel.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-19 (score 75)

First indexed and scored.

## MCP tools (4)

### `regimen_describe_factors` (~72 tokens)

Describe regime 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.

Output parameters:

- `factors` (array)
- `note` (string)

### `regimen_evaluate_track_record` (~269 tokens)

Evaluate a 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 — 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.

Input parameters:

- `benchmarkSharpe` (number): Per-period Sharpe the record must beat. 0 asks only whether there is any edge at all.
- `confidence` (number)
- `detail` (string): 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, required): Which track record to analyse.
- `trialSharpes` (array): 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…

Output parameters:

- `deflatedSharpe` (number|null)
- `divergencesFromReported` (array)
- `full`: The complete report when detail is "full", otherwise null.
- `headline` (string)
- `label` (string)
- `minimumTrackRecordLength` (number|null)
- `notes` (array)
- `periodsShortOfSignificance` (number|null)
- `probabilisticSharpe` (number|null)
- `reasoning` (array)
- `sharpeAnnualised` (number|null)
- `sharpeConfidenceInterval`
- `sharpePerPeriod` (number|null)
- `sourceId` (string)
- `usableReturns` (number)
- `verdict` (string): One of insufficient_evidence, indistinguishable_from_luck, weak, supported, strong.

### `regimen_regime_map` (~219 tokens)

Map performance to market regimes

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.

Input parameters:

- `detail` (string): 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): How many of the most recent dates to read conditions for, bounded by the upstream rate limit.
- `minSample` (integer): Buckets below this many observations are returned but flagged unusable.
- `selector` (object, required): Which track record to analyse.

Output parameters:

- `datesCovered` (number)
- `factors` (array)
- `full`
- `label` (string)
- `minSample` (number)
- `warnings` (array)

### `regimen_self_attack` (~120 tokens)

Attack the verdict

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.

Input parameters:

- `selector` (object, required): Which track record to analyse.
- `simulations` (integer)

Output parameters:

- `controls` (array)
- `label` (string)
- `notes` (array)
- `nullDistribution`
- `verdict` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rayyer220-regimen/regimen-nu#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 75

## Common questions

### What is the io.github.RaYYeR220/regimen MCP server?

io.github.RaYYeR220/regimen is an MCP server listed in the public MCP registry as io.github.RaYYeR220/regimen. Tells you whether a trading strategy's edge is distinguishable from luck. This page covers its hosted endpoint (https://regimen-nu.vercel.app/mcp).

### Is the io.github.RaYYeR220/regimen MCP server safe to use?

io.github.RaYYeR220/regimen scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.RaYYeR220/regimen MCP server expose?

io.github.RaYYeR220/regimen exposes 4 tools: regimen_describe_factors, regimen_evaluate_track_record, regimen_regime_map, regimen_self_attack. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.

### Does the io.github.RaYYeR220/regimen MCP server require authentication?

No. We connected to io.github.RaYYeR220/regimen without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.RaYYeR220/regimen MCP server still maintained?

io.github.RaYYeR220/regimen is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://regimen-nu.vercel.app/mcp
- Repository: https://github.com/RaYYeR220/regimen
- Website: https://regimen-nu.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/rayyer220-regimen/regimen-nu.xml
- Changelog JSON feed: https://verifymcp.io/servers/rayyer220-regimen/regimen-nu.json
- HTML version of this page: https://verifymcp.io/servers/rayyer220-regimen/regimen-nu