com.alphaassay/mcp
com.alphaassay/mcp · 0.6.1
Fail-closed backtest/signal validation: overfitting, leakage, deflated Sharpe. NOT financial advice.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.alphaassay.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 21 tools.
- Protocol
- 2025-06-18
- Calls itself
- alphaassay 1.28.1
- Handshake time
- 424 ms
- HTTP status
- 200
The tools it lists (21, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
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. A methodology audit; no buy/sell advice. Free demo verdict -- see AlphaAssay's full output shape in one call. Runs the real fail-closed validator over a built-in 40-trade example and returns the complete verdict envelope (verdict, qualitative findings, leakage taxonomy, provenance hashes) plus the machine-readable remediation explanation -- and a free synthetic-null preview: three seeded no-edge worlds (Heston stochastic volatility, Merton j
assay_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. Validate a trading strategy export: fail-closed statistical verdict. Reality-check for backtest results, trade lists and equity curves (overfitting detection, deflated Sharpe, multiple-testing deflation via n_trials, cost stress, look-ahead signature, sample-size floor). Accepts CSV text (trade list with pnl / return %, equity curve, signal series) or a QuantConnect/LEAN backtest JSON -- crypto, s
assay_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. Independently recompute a claimed track record -- audit the arithmetic, not the story. New audit object: not the signal, the CALLER'S CALCULATION. Send the trades (entry/exit time, price, side), the candles they were filled on, and the claimed headline metrics (total_return_pct, win_rate, max_drawdown_pct, n_trades, sharpe_annualized); the engine rebuilds the equity book independently and grades the claim against di
assay_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. Interrogate a raw fill log for internal contradictions -- no candles needed. assay_preflight lints shape, assay_reproduce audits arithmetic against candles; this tool needs nothing but the log itself and asks whether it is internally consistent: exact duplicate fills (double counting inflates every headline number: tradelog_duplicate_fills), time travel (exits before entries, decisions stamped AF
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.alphaassay/mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 79 days ago. The registry entry · alphaassay.com