Skip to content
AlphaAssay logo

AlphaAssay MCP server

Which servers in the official MCP registry are AlphaAssay's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to AlphaAssay

Whose server it is
  • Registry namecom.alphaassay/mcpverified in the MCP registry

The registry name sits under alphaassay.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools21
  • Server calls itselfalphaassay
  • Server version1.28.1
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 515 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • Its definitions take about 29276 tokens of context: enable only the tools a task needs.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer487 ms
  • Space in an agent's context≈ 29,276 tokensthe definitions of all its tools (21), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results21 of 21 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers21 tools · read 2026-10-24
  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "alphaassay": {
      "type": "http",
      "url": "https://mcp.alphaassay.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http alphaassay https://mcp.alphaassay.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.alphaassay.com/mcp as a custom connector in the settings.

OpenAPI spec

42 paths, read 2026-10-24. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.