regimen

Name: regimen
Author: RaYYeR220

MCP serverMCP

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

by RaYYeR220repository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"regimen","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability77/77 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	147 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
10 h ago	mcp initialize	ok	200	152 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
16 h ago	mcp initialize	ok	200	163 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
23 h ago	mcp initialize	ok	200	164 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
30 h ago	mcp initialize	ok	200	163 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	143 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	456 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	136 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	186 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools
3 d ago	mcp initialize	ok	200	156 ms	server regimen 1.0.0 · protocol 2025-06-18 · 4 tools

Tools observed via MCP handshake

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 yo
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 b
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
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 popul

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.RaYYeR220/regimen

first seen 21 d ago · fetched 2 d agoopen ↗

Field history (7 recent events)

21 d ago · declared · summary → "Tells you whether a trading strategy's edge is distinguishable from luck."
21 d ago · declared · description → "Tells you whether a trading strategy's edge is distinguishable from luck."
21 d ago · declared · publisherName → "RaYYeR220"
21 d ago · declared · homepageUrl → "https://regimen-nu.vercel.app"
21 d ago · declared · repoUrl → "https://github.com/RaYYeR220/regimen"
21 d ago · declared · version → "1.0.0"
21 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from