alphaassay/mcp
AlphaAssay is a signal validation and overfitting forensics platform that statistically audits trading signals, backtests, and strategies — returning deterministic pass/fail verdicts with signed, replayable audit records.
Free tools
assay_demo— Run a free demo to see the full output schema and known-verdict specimens.assay_graveyard— Look up anonymised falsification statistics for a signal family before investing time in an idea.assay_calibration— View AlphaAssay's own signed public calibration and verdict hit-rate.assay_certificate_verify— Offline Ed25519 signature verification of a signed verdict certificate.assay_provider_protocol— Get a machine-readable 7-test falsification checklist to audit any signal provider.assay_preflight— Lint a payload (DSL schema, OHLCV data, trade rows) before spending a paid check.
Signal & backtest validation
assay_signal— Validate a trading strategy export with deflated Sharpe, multiple-testing correction, overfitting detection, look-ahead checks, and cost stress.assay_backtest— Run a deterministic DSL backtest with honest family-level trial accounting.assay_gauntlet— Full reality-check battery: validator, family deflation, placebo, capacity ceiling, and graveyard prior in one call.assay_falsify— Actively stress-test a signal with adversarial attacks (execution lag, cost stress, time jackknife, regime split, parameter perturbation).
Overfitting & forensics
assay_forensics— Diagnose look-ahead leakage, front-loading, random timing comparison, and event independence.assay_pbo— Compute Probability of Backtest Overfitting (CSCV) over a full parameter payoff matrix.assay_survivors— Apply Romano-Wolf stepwise FWER control to disclose which variants survive family-wise error budgeting.assay_batch— Submit up to 25 parameter sweep variants in one call with cumulative deflation applied.
Reproducibility & pre-registration
assay_reproduce— Independently recompute a claimed track record from trades + candles, grading metrics against disclosed tolerances.assay_register— Pre-register a hypothesis with a tamper-proof Merkle-anchored timestamp, making the later verdict immune to overfitting.assay_verdict— Fetch a post-cutoff verdict for a pre-registered signal, enforcing sealed hypothesis terms.
alphaassay-tools
Open-source client tooling for the AlphaAssay validation service: an offline certificate verifier (Python) and a stdio-to-remote MCP proxy (Node), plus runnable examples and the registry manifest for the hosted server.
Component | Language | Path | What it does |
| Python ≥3.10 | Verifies certificates offline: Ed25519 signatures, canonical serialisation, signed key/revocation history. No network access. | |
MCP proxy | Node ≥18 | Bridges a local stdio MCP client to the remote streamable-HTTP endpoint. | |
Examples | — | Known-answer request/response pairs you can run against the free demo endpoint. | |
| — | Secondary artifact: the manifest the MCP registry reads to describe the hosted server. Not needed to use the code above. |
The validation engine itself is a hosted service and is not part of this repository.
Install
Python verifier, from source:
pip install .
# or, for development
pip install -e ".[dev]"Node proxy:
npm installRelated MCP server: OpenInvest
Usage
Verify a certificate offline
Full platform trust needs three local inputs: the certificate with its signature, a signed version-2 revocation/key-history bundle, and at least one externally obtained SHA-256 root fingerprint. The verifier performs no network or database access.
python -m alphaassay_verify verify \
--certificate cert.json \
--trust-bundle trust-bundle.json \
--root-fingerprint <64-hex-digest>Signature-only evidence, when you deliberately do not want to establish full platform trust:
python -m alphaassay_verify signature-only \
--certificate cert.json \
--public-key key.pemExit code 0 means verified; a non-zero exit code and a machine-readable
reason mean it is not. See SPEC.md for the canonical byte format
and the trust rules the implementation follows.
Run the MCP proxy
node server/index.mjsThe proxy speaks stdio to your MCP client and forwards to the remote endpoint.
The tool list it exposes is in server/tools.json.
Run the examples
Each example is a request payload, the expected response, and a shell script that posts it to the free demo endpoint:
cd examples && ./golden_lookahead.shThe expected responses are checked in, so they double as fixtures for integration tests in your own code.
Tests
python -m pytest tests/ # verifier: unit tests and canonical vectors
npm test # proxy: contract and behaviour testsTest vectors live in tests/canonical_vectors.json
and tests/fixtures/; they are the same vectors the
implementation is developed against.
Contributing
Issues and pull requests are welcome. Please:
keep changes focused and include tests for behaviour changes;
run
python -m pytest tests/andnpm testbefore opening a PR;for the verifier, do not add network or database access — offline operation is a design constraint, not an implementation detail;
report security issues privately as described in
SECURITY.mdrather than in a public issue.
License
Apache-2.0. See LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityBmaintenanceAI-native quantitative trading signal engine for crypto and TradFi perpetuals. Multi-factor composite BUY/SELL/HOLD signals, cross-venue funding rate arbitrage scanning, and market regime detection powered by Hyperliquid data.75355MIT
- AlicenseAqualityAmaintenanceInvestment decision tools for AI agents: portfolio status, isolated multi-agent committee analysis, auditable verdict history, and lookahead-protected backtests. Advisory only, no auto-trading; negative research results published.2181MIT
- AlicenseNot gradedqualityAmaintenanceDeterministic market-state engine for trading agents — zero LLM in the signal path. 8 tools: structural market state & phase, action gate (GO/WATCH/HOLD), entry/target/invalidation coordinates, bar-by-bar state timeline, composed view cards, and pre-trade intent validation. Every output traces to a bar-stamped ledger with a public daily self-scoring track record.3MIT
- AlicenseBqualityAmaintenanceVerify a number before an agent asserts it — a Deflated Sharpe Ratio for backtest, plus eval-gap, subset-win, and judge-bias checks, with signed receipts anyone can verify offline.34MIT
Related MCP Connectors
Validated trading edges across futures, equities, crypto. Live signals, full audit trail.
Grade a track record before risking capital: REAL_EDGE/REGIME_LUCK/NEGATIVE_EV. Fail-closed.
Crypto backtesting & Bitcoin cycle analytics. Point-in-time, DSR-corrected, look-ahead-aware.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alphaassay/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server