Analytics
alphaassay.com
Provides auditing and forensic analysis of trading track records and backtest results to detect overfitting, data leakage, and other validity issues.
ENDPOINT 1
https://mcp.alphaassay.com/mcp
MCP server metadata
- Name
- alphaassay
- Version
- 1.28.1
AlphaAssay -- the independent assay office for trading signals. Code-computed, fail-closed statistical validation of trading strategies, backtests and signals: deflated Sharpe with cumulative trial accounting, leakage forensics, pre-registration whose terms are committed now and queued for later operator-published Merkle inclusion (independent time evidence requires a separately pinned external anchor), and anonymised graveyard statistics over falsified signal families. Gauntlet and other typed dossier outputs expose surface-specific gradient fields; inspect each tool schema instead of assuming universal fields. For example, Gauntlet exposes its first failed stage, machine-readable failure codes, requested matched-placebo count, adversarial survival map, and family trial budget. Relay available specifics to your operator instead of a bare fail. Expect failure: peer-reviewed base rates say most apparent edges are selection noise (Harvey/Liu/Zhu 2016; Bailey/Lopez de Prado 2014); a fail with a named cause is the product working, not failing. The platform grades itself publicly: the current persisted calibration snapshot via assay_calibration, anonymised family mortality via assay_graveyard. assay_pbo grades your whole parameter sweep at once (probability of backtest overfitting, CSCV); assay_batch submits the sweep itself -- every variant a ledger trial; assay_preflight (free) lints your payload before you spend a check; assay_provider_protocol (free) hands you the seven-test falsification protocol for judging ANY signal seller -- including us. Demote-only: verdicts can devalue a signal, never bless one. Certificates are separately issued and offer offline raw-signature verification; full platform trust additionally requires an independently pinned keyring and fails closed without it (assay_certificate_verify). Works for crypto, equities, futures and FX -- the statistics are asset-agnostic. NOT financial advice; no order path. Start with assay_demo (free), look up your idea's family in assay_graveyard (free), then submit via assay_signal. The tool surface grows continuously: this handshake's tools/list is the always-current machine truth, and https://alphaassay.com/docs/tools documents every tool in depth (machine-readable prices: https://api.alphaassay.com/v1/meta/pricing).
Known tools 21
assay_demoUse this when you want to see AlphaAssay's exact verdict envelope -- schema, findings, leakage taxonomy -- on a built-in example before spending a check.
Inferred read-onlyassay_signalUse this when you have a backtest result or live track record (a trades log, equity curve or QuantConnect export) and need to know whether the edge is real or just overfitting, survivorship or luck.
Inferred read-onlyassay_reproduceUse this when someone hands you a claimed track record and you want to recompute it yourself from the fills and candles -- an arithmetic audit of the numbers, not buy/sell advice.
Inferred read-onlyassay_tradelogUse this when you have a raw fill or trade log and want it scanned for internal contradictions -- look-ahead timestamps, pnl that disagrees with the row's own prices, duplicate or out-of-order fills.
Potential side effectsassay_forensicsUse this when a signal looks good but you suspect leakage or look-ahead and want to know WHY it fails, not just that it fails -- a diagnostic audit, it does not give buy/sell advice.
Inferred read-onlyassay_backtestUse this when you want a code-computed DSL backtest whose deflated- Sharpe verdict still means something after repeated searching -- every run is priced into your family's trial ledger.
Inferred read-onlyassay_gauntletUse this when you want the whole reality-check battery on a strategy in one call -- overfitting, leakage, costs, regimes and a matched-random placebo -- as a demote-only dossier, never buy/sell advice.
Inferred read-onlyassay_falsifyUse this when you want your strategy actively attacked -- execution lag, cost stress, regime split, parameter neighbourhood, drift-burst -- to see what kills it first.
Inferred read-onlyassay_pboUse this when you have the T x N returns of a grid search and want the probability of backtest overfitting (PBO, CSCV) -- did the sweep find an edge or manufacture one?
Inferred read-onlyassay_var_esUse this when you have VaR or Expected-Shortfall forecasts and need to know whether reality breached them more often or deeper than your claimed tail level allows -- a risk-forecast audit, not buy/sell advice.
Inferred read-onlyassay_conformalUse this when your model emits prediction intervals or confidence bands and you want to audit whether realised outcomes actually fall inside them at the claimed coverage -- a calibration audit, not advice.
Inferred read-onlyassay_survivorsUse this when you ran a grid or parameter sweep and want to know WHICH variants survive family-wise error control (FWER) rather than surfacing by chance -- an error-budget disclosure, not buy/sell advice.
Inferred read-onlyassay_cpcvUse this when you have a return history and want the full combinatorial purged cross-validation (CPCV) distribution -- not one walk-forward number -- to see how path-dependent the edge really is.
Inferred read-onlyassay_batchUse this when you optimised over a grid and want to submit the WHOLE sweep honestly -- every variant a ledger trial the family budget prices, so selection bias cannot hide.
Inferred read-onlyassay_registerUse this when you want to seal a strategy and its success criteria NOW, before the forward data exists, so that registration cannot be adapted or backfilled against those later bars -- a commitment audit, not buy/sell advice.
Inferred read-onlyassay_verdictUse this when a signal was pre-registered with assay_register and the maturity window has passed -- get the post-cutoff verdict computed only from data after registration.
Potential side effectsassay_graveyardUse this when you want to check, for free, how often a signal family (e.g.
Inferred read-onlyassay_calibrationUse this when you want to inspect AlphaAssay's current public calibration state for free rather than trust marketing.
Inferred read-onlyassay_certificate_verifyUse this when someone hands you a signed AlphaAssay certificate and you want to verify both its Ed25519 signature and current platform trust.
Inferred read-onlyassay_provider_protocolUse this when you want to judge ANY signal seller -- including us -- with a machine-readable seven-test falsification protocol you can run in an afternoon.
Inferred read-onlyassay_preflightUse this when you want to lint the SHAPE of a submission (DSL spec, candles or trades) for free before spending a check, so a typo never costs you one.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.alphaassay]
url = "https://mcp.alphaassay.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"alphaassay": {
"type": "http",
"url": "https://mcp.alphaassay.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: alphaassay
Remote MCP URL: https://mcp.alphaassay.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"alphaassay": {
"url": "https://mcp.alphaassay.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"alphaassay": {
"type": "http",
"url": "https://mcp.alphaassay.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "alphaassay",
"transport": "streamable-http",
"url": "https://mcp.alphaassay.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for alphaassay.com was fetched 2026-07-26T07:12:42.535Z.
alphaassay.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.