Canli Validation Mcp
canlicapital.com backtest validation. A verdict is not admission to anything and is not a forecast.
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.arhancanli/canli-validation-mcp
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
The public site for Canli Capital, and the surface where ALPHAC — a four-sleeve cross-asset quant book — publishes its record while it is still small enough to be embarrassing.
Created and maintained by Arhan Canli for Canli Capital.
Development uses reviewed AI-assisted tooling, while project ownership, research decisions,
published claims, and release responsibility remain with Arhan Canli.
Machine-readable software citation metadata is provided in CITATION.cff.
The engine that produces every number here is open too: github.com/arhancanli/alphac.
Live: canlicapital.com
Build with it: get an API key, connect the MCP server, or contribute a reproducible improvement. If the project is useful, star the repository to help other developers find it.
Current work and verified limitations: persistent goal status.
Why this repo is public
The site's whole claim is "a quant fund proving itself in public before it asks you to trust
it." — the tagline in config/brand.js. A site that makes that claim and hides its own source
is asking for a trust it hasn't earned. So: this is the source, including the parts that enforce
honesty on us.
The load-bearing one is docs/retracted_claims.txt in the engine repo. When a number is
withdrawn it goes on a blocklist, and check_retracted_claims.py scans dist/ and public/ for
it before each deploy. It cannot be satisfied by deleting the number — a retracted figure must
still be quotable inside its own retraction, so a match counts only when the explanation is
absent from the surrounding window.
That check exists because the retraction here had already failed twice: a withdrawn DSR of 0.83 stayed on the homepage and in the social-unfurl card for six days after the signed chain formally withdrew it. The pipeline was publishing the correction and the error in the same run.
The gate is now fail-closed for publication. Since 2026-08-19, both live_tick.sh and
live_publish.sh run check_retracted_claims.py after regeneration and skip the deploy when it
fails. Trading remains outside that blast radius: a publication defect can stop the website from
shipping, but cannot place, cancel, or delay an order.
Publication surfaces
From the project's README.