Alphaassay is an MCP server with 21 tools an agent can call, among them assay_backtest, assay_batch, assay_calibration. It answers at https://mcp.alphaassay.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Fail-closed backtest/signal validation: overfitting, leakage, deflated Sharpe. NOT financial advice.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
assay_backtest | Use 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. A research audit, not buy/sell advice. Ledger-aware DS Inputs: spec, ohlcv_by_symbol, fee_bps_per_side, variants_in_call, sketch_opt_out, api_key |
assay_batch | Use 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. A research audit, not buy/sell advice. Submit your WHOLE parameter |
assay_calibration | Use this when you want to inspect AlphaAssay's current public calibration state for free rather than trust marketing. Calibration v0 is a population/status disclosure, not an outcome score or track record. Self-calibration of the validator' |
assay_certificate_verify | Use this when someone hands you a signed AlphaAssay certificate and you want to verify both its Ed25519 signature and current platform trust. A verification tool, not buy/sell advice. Verify a signed AlphaAssay certificate against externall Inputs: certificate, signature_b64, public_key_pem |
assay_conformal | Use 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. Does your model's confidence label Inputs: intervals_lower, intervals_upper, outcomes, claimed_coverage, calibration_size, api_key |
assay_cpcv | Use 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. The FULL combinatorial purged CV distributio |
assay_demo | Use this when you want to see AlphaAssay's exact verdict envelope -- schema, findings, leakage taxonomy -- on a built-in example before spending a check. A methodology audit; no buy/sell advice. Free demo verdict -- see AlphaAssay's full ou |
assay_falsify | Use this when you want your strategy actively attacked -- execution lag, cost stress, regime split, parameter neighbourhood, drift-burst -- to see what kills it first. Demote-only; it does not give buy/sell advice. We do not check your sign Inputs: spec, ohlcv_by_symbol, fee_bps_per_side, api_key, request_id |
assay_forensics | Use 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. Leakage forensics: WHY your signal fails, not just that i Inputs: signal_events, ohlcv_by_symbol, primary_horizon, api_key, request_id |
assay_gauntlet | Use 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. The full reality-check battery in ONE |
assay_graveyard | Use this when you want to check, for free, how often a signal family (e.g. sma_cross) has already been falsified and what usually kills it, before spending a check. Anonymised stats only -- no buy/sell advice. Free lookup: how often has thi Inputs: strategy, variant, timeframe, fingerprint |
assay_pbo | Use 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? A demote-only audit, not buy/sell advice. Did your parameter sweep FIND Inputs: returns_matrix, n_groups, purge, embargo, periods_per_year, api_key |
assay_preflight | Use 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. A format check only -- it gives no buy/sell advice. Free payload lint -- fix your submis Inputs: spec, ohlcv_by_symbol, trades |
assay_provider_protocol | Use 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. It scores methodology, not markets: no buy/sell advice. Test ANY signal provider in |
assay_register | Use 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. Pre-register a Inputs: spec, maturity_bars, embargo_bars, hypothesis, api_key, request_id |
assay_reproduce | Use 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. Independently recompute a claimed track record -- audit the Inputs: trades, ohlcv_by_symbol, claimed, fee_bps_per_side, api_key, request_id |
assay_signal | Use 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. Validate a trading strategy export: fail- |
assay_survivors | Use 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. WHICH variants of your sweep surviv Inputs: returns_matrix, alpha, n_bootstrap, block_length, periods_per_year, api_key |
assay_tradelog | Use 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. Interrogate a raw fill log for internal Inputs: trades, trading_calendar, api_key, request_id |
assay_var_es | Use 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. Does your risk model's VaR/ES Inputs: returns, var_forecasts, es_forecasts, alpha, benchmark_var_forecasts, benchmark_es_forecasts |
assay_verdict | Use 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. A sealed audit, it gives no buy/sell advice. Post-cutoff verdict und Inputs: prereg_id, ohlcv_by_symbol, fee_bps_per_side, trading_calendar, api_key, request_id |
Every block below points at https://mcp.alphaassay.com/mcp. Pick your client and copy.
claude mcp add --transport http alphaassay https://mcp.alphaassay.com/mcp
{
"mcpServers": {
"alphaassay": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.alphaassay.com/mcp"]
}
}
}{
"mcpServers": {
"alphaassay": {
"url": "https://mcp.alphaassay.com/mcp"
}
}
}{
"servers": {
"alphaassay": {
"type": "http",
"url": "https://mcp.alphaassay.com/mcp"
}
}
}{
"context_servers": {
"alphaassay": {
"url": "https://mcp.alphaassay.com/mcp"
}
}
}{
"mcpServers": {
"alphaassay": {
"serverUrl": "https://mcp.alphaassay.com/mcp"
}
}
}{
"mcpServers": {
"alphaassay": {
"url": "https://mcp.alphaassay.com/mcp"
}
}
}name: Alphaassay
version: 0.0.1
schema: v1
mcpServers:
- name: Alphaassay
type: streamable-http
url: https://mcp.alphaassay.com/mcp{
"mcpServers": {
"alphaassay": {
"httpUrl": "https://mcp.alphaassay.com/mcp"
}
}
}{
"mcpServers": {
"alphaassay": {
"type": "http",
"url": "https://mcp.alphaassay.com/mcp"
}
}
}{
"mcpServers": {
"alphaassay": {
"url": "https://mcp.alphaassay.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.alphaassay.com%2Fmcp&type=streamable_http&id=alphaassay&name=Alphaassay
It answered our last check on 17 October 2026 in 80 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by alphaassay.com and served from mcp.alphaassay.com, the vendor's own domain: https://mcp.alphaassay.com/mcp.
21, as returned by the server's own tools/list on 10 September 2026: assay_backtest, assay_batch, assay_calibration, assay_certificate_verify, assay_conformal, assay_cpcv, assay_demo, assay_falsify, and 13 more.
It answered our last check on 17 October 2026 in 80 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.alphaassay.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.alphaassay. Endpoint host: mcp.alphaassay.com. ARD identifier: urn:air:com.alphaassay:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.