Regime

Name: Regime
Author: xyz.regimetoken

MCP serverMCP

Checks crypto trading claims on real data: leverage, drawdown, stop-loss, seasonality, luck.

by xyz.regimetokenhomepage ↗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":"regime","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 availability26/26 checks ok

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	110 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
8 h ago	mcp initialize	ok	200	63 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
15 h ago	mcp initialize	ok	200	115 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
22 h ago	mcp initialize	ok	200	63 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
29 h ago	mcp initialize	ok	200	65 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	68 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	62 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	75 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
2 d ago	mcp initialize	ok	200	88 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools
3 d ago	mcp initialize	ok	200	102 ms	server regime 1.0.0 · protocol 2025-06-18 · 12 tools

Tools observed via MCP handshake

strategy_grid_lookup — Backtest lookup: what one exact version of a strategy actually did. Buy-the-dip and the moving-average cross, every combination of their knobs, computed over ni
overfitting_odds — Overfitting check: how many attempts plain chance needs to produce the track record you were shown. Give the wins, the losses and how many versions were tried:
leverage_survival — What a leveraged trade actually did, opened on every single day of the history instead of the one day that worked. Give coin, side, leverage and holding period:
drawdown_check — Drawdown check: what it cost to collect the return you were shown. The coin is bought at the close of every day of its history and held for the period you name:
diversification_check — Diversification check: how many independent bets a basket of coins really is. Give the coins (and optionally the window: 90, 365 or 730 days): you get the avera
averaging_in_check — Whether spreading the entry would have helped, measured. One amount into a coin over a window (90, 365 or 730 days): all of it on day one, or equal instalments
stop_loss_check — Whether a stop-loss would have helped, measured. The same buy of a coin, held 30, 90, 365 or 730 days, with a stop 5, 10, 15, 20 or 30% below the entry and with
copy_trading_check — Whether copying the top traders works, measured. Accounts in the top 10% or 1% of Hyperliquid one month, by return or by dollar profit: how many were in the top
leaderboard_rank_check — How much company a return has. Send a return (+340%) and a window (day, week, month or all time) and get how many accounts on Hyperliquid's whole public leaderb
calendar_check — 'Uptober'. 'Mondays dip'. 'Sell in May'. Any calendar claim on 34 coins, measured against chance. With seven days one has to come first, so the answer is a perm
best_days_check — The 'miss the ten best days and you get nothing' claim, measured on both sides. The same window of a coin lived four ways: all of it, without its N best days, w
coin_comparison — Two or three coins side by side, every check at once: for each, how often a buy fell 30% or more before the window was out and where the middle one ended, how o

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

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 Registryxyz.regimetoken/regime

first seen 7 d ago · fetched 31 h agoopen ↗

Field history (6 recent events)

7 d ago · declared · summary → "Checks crypto trading claims on real data: leverage, drawdown, stop-loss, seasonality, luck."
7 d ago · declared · description → "Checks crypto trading claims on real data: leverage, drawdown, stop-loss, seasonality, luck."
7 d ago · declared · publisherName → "xyz.regimetoken"
7 d ago · declared · homepageUrl → "https://regimetoken.xyz/api"
7 d ago · declared · version → "1.0.0"
7 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from