Servidor MCP de AlphaAssay

• Nombre en el registrocom.alphaassay/mcpverificado en el registro MCP

El nombre en el registro está bajo alphaassay.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-24
• Herramientas21
• El servidor se llamaalphaassay
• Versión del servidor1.28.1
• Versión del protocolo2025-06-18

El 2026-10-24 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 515 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 1 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 1 hasta ahora
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta487 ms
• Espacio en el contexto del agente≈ 29.276 tokenslas definiciones de todas sus herramientas (21), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados21 de 21 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

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