io.github.RaYYeR220/regimen
REMOTE · REGIMEN-NU.VERCEL.APP · SCANNED SEP 20
Tells you whether a trading strategy's edge is distinguishable from luck.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1140 tokens (~81/item across 14 items; 4 tools + 10 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · regimen-nu.vercel.app
claude mcp add --transport http rayyer220-regimen 'https://regimen-nu.vercel.app/mcp'
{
"mcpServers": {
"rayyer220-regimen": {
"url": "https://regimen-nu.vercel.app/mcp"
}
}
} {
"servers": {
"rayyer220-regimen": {
"type": "http",
"url": "https://regimen-nu.vercel.app/mcp"
}
}
} [mcp_servers.rayyer220-regimen] url = "https://regimen-nu.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rayyer220-regimen": {
"type": "remote",
"url": "https://regimen-nu.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add rayyer220-regimen --url 'https://regimen-nu.vercel.app/mcp' --transport streamable-http
mcp_servers:
rayyer220-regimen:
url: "https://regimen-nu.vercel.app/mcp" {
"McpServers": {
"rayyer220-regimen": {
"Transport": "http",
"Url": "https://regimen-nu.vercel.app/mcp"
}
}
} assistant mcp add rayyer220-regimen -t streamable-http -u 'https://regimen-nu.vercel.app/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://regimen-nu.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of regimen-nu.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://regimen-nu.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://regimen-nu.vercel.app/mcp | HTTPS enforced | 308 | https://regimen-nu.vercel.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
regimen_describe_factors Describe regime factors ~72
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| factors | array | yes | – |
| note | string | yes | – |
No examples provided.
regimen_evaluate_track_record Evaluate a track record ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| deflatedSharpe | number|null | yes | – |
| divergencesFromReported | array | yes | – |
| full | – | yes | The complete report when detail is "full", otherwise null. |
| headline | string | yes | – |
| label | string | yes | – |
| minimumTrackRecordLength | number|null | yes | – |
| notes | array | yes | – |
| periodsShortOfSignificance | number|null | yes | – |
| probabilisticSharpe | number|null | yes | – |
| reasoning | array | yes | – |
| sharpeAnnualised | number|null | yes | – |
| sharpeConfidenceInterval | – | yes | – |
| sharpePerPeriod | number|null | yes | – |
| sourceId | string | yes | – |
| usableReturns | number | yes | – |
| verdict | string | yes | One of insufficient_evidence, indistinguishable_from_luck, weak, supported, strong. |
No examples provided.
regimen_regime_map Map performance to market regimes ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Which track record to analyse. |
| Name | Type | Req | Description |
|---|---|---|---|
| datesCovered | number | yes | – |
| factors | array | yes | – |
| full | – | yes | – |
| label | string | yes | – |
| minSample | number | yes | – |
| warnings | array | yes | – |
No examples provided.
regimen_self_attack Attack the verdict ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| selector | object | yes | Which track record to analyse. |
| simulations | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| controls | array | yes | – |
| label | string | yes | – |
| notes | array | yes | – |
| nullDistribution | – | yes | – |
| verdict | string | yes | – |
No examples provided.
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.