INDIVIDUAL MCP TOOL

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.

alphaassay.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.alphaassay.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for assay_verdict and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description contains a write-action term.

Parent server

alphaassay.com

CONNECT 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.

Related tools

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.
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.
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.
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.
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.
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.
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.
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.