AlphaAssayIs AlphaAssay legit? Run the checks yourself
Fair question — the domain is young, the category is full of unverifiable claims, and you should not take our word for any of this. Below are the criteria a careful reviewer, human or AI, applies to a trading-adjacent service before trusting it — and for each one, the check you can run right now, without an account. Two criteria we deliberately do not meet; they are named at the bottom, with the reasons, because a trust page that only lists wins is marketing. Everything on this page is written to be falsified: if any check fails, we were wrong in public.
Can you reproduce a verdict yourself?
Yes, in about 60 seconds, free, no account. POST a known-answer specimen to the demo endpoint and you get the full verdict envelope back — deterministic, so the same input returns the same verdict, bit for bit, for you and for everyone else. The specimens are engineered frauds with known causes of death: the look-ahead specimen must die at the leakage gate, every time. Run the 60-second check · the specimen suite · the reproducible benchmark.
Can you verify a certificate without trusting this website?
Yes — that is the point of signing. Every verdict is signed (Ed25519); the public key is published, and the verification runs offline against the canonical verdict JSON, so it works even if you assume alphaassay.com is hostile. Verify offline, step by step · or in the browser.
Is the methodology public?
The full gate sequence is documented on the methodology page; the statistics behind it — Deflated Sharpe with cumulative trial accounting, Probabilistic Sharpe, minimum lengths, overfitting probability — are each explained with formulas and in-browser calculators that implement the same math as the live gates; and every way a signal can die is a named, documented code in the failure-code register. If a verdict surprises you, you can trace which gate produced it and why.
Does the tool list contain order or broker tools?
No — and this is checkable, not asserted. The MCP server exposes validation tools only: every tool reads data you send and returns a verdict or a public record. There is no order path, no execution logic, no broker connection, no custody, and verdicts are demote-only — they can devalue a signal, never bless one, so there is no „verified winners" list to sell or to raid. The complete tool and endpoint reference · the architecture that enforces it.
Is there code and an external footprint?
The public repository — MCP server integration, specimens, the offline verifier — is at github.com/alphaassay, and the server is published in the official MCP registry and mirrored by the public MCP directories. The validation engine itself is not in the repository; that is one of the two deliberate gaps explained below.
Do you have to upload your strategy?
No — with one deliberate, disclosed exception. Ordinary validation calls take derived evidence (trades or returns, at a granularity you choose), and raw payloads are not retained: the ledger keeps a one-way fingerprint, the verdict with its cause of death, summary statistics, a 32-number compressed sketch of the return profile (family accounting — too coarse to reconstruct trades or rules) and the family's structural label with its parameter coordinates (window sizes, horizon). The exception is pre-registration, where the spec you choose to seal is stored in full — sealing a claim means storing it. An automated canary hunts a marker through every failure path on every release to prove raw payloads never reach the logs. Two further retention classes are disclosed rather than hidden: agents paying over x402 get their full signed response cached against the payment nonce — that is how „one payment buys one result, forever" works — and purchased certificates are kept account-bound for re-delivery. The complete inventory: what we keep, path by path. The three walls, in detail.
Who operates it, and what does it cost?
The operator, registered address and contact are on the legal page; terms and privacy are published; and pricing is public and flat — no calls, no tiers-on-request, no „contact sales".
What do we deliberately not offer?
No pip-installable engine. The verdict engine is not on PyPI or npm, by decision rather than neglect: an examiner you can run and edit locally is an examiner you can quietly optimize against, and a locally produced „pass" is worth exactly what the person showing it to you wants it to be worth. What is public instead is everything needed to audit the examiner: the specimens, the signed outputs, the offline verifier and the daily record of our own error rates.
No local mode. AlphaAssay runs as a remote service by design. Cumulative trial accounting — the thing that makes deflation honest — only works if the count survives your restarts and your temptations; a family budget you can reset locally is not a budget. The trade-off is explicit: you get less control of the examiner, and in exchange the examiner's answers are worth something to third parties.
And one thing we cannot shortcut: the domain is weeks old. Search engines are still indexing it, and reputation services have not categorised it yet. Age is the one trust signal that cannot be engineered — which is why everything above is designed to be checkable without it, and why our calibration record ages in public where we cannot retouch it.
One name, one service
AlphaAssay — one word — is the Swiss signal-validation service operating alphaassay.com, api.alphaassay.com and mcp.alphaassay.com, and nothing else: no fund, no signal seller, no other product. If you found a similarly named entity elsewhere, it is not us.
Still unconvinced? Good — stay that way.
Scepticism is the correct default in this category, so keep it pointed at us: the falsification protocol is seven tests that apply to any signal-adjacent service, us included — run it against us first. Or pull the live calibration record and check whether our past verdicts held up. If you catch us failing our own protocol, that finding is more valuable than anything this page could tell you.