canli-validation-mcp
Related Servers
Alternatives to canli-validation-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables auditing and verification of algorithmic trading backtests from coding agents like Claude Code, Cursor, and Windsurf, including look-ahead bias detection, overfitting checks, and sealed audit proof verification.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
- FlicenseNot gradedqualityFmaintenanceProvides financial data and market filings via Streamable HTTP tools. Enables AI agents to resolve equity entities, fetch SEC filings, compare institutional holders, and export finance receipts.-
- AlicenseNot gradedqualityBmaintenanceProvides tools to research crypto trading strategies via backtesting, walk-forward validation, and paper trading, with a deflated-Sharpe overfitting check. Enables natural-language-driven analysis and interpretation of strategy performance.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents and people to run local SEC research queries against EDGAR or demo fixtures, returning verifiable financial data, filing text, charts, and evidence packets with explicit source and coverage.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides MCP tools that let AI agents retrieve stock price data, validate data quality, analyze chart trends and volatility, and fetch news sentiment, enabling structured financial analysis workflows.-
TDQS
Scored across 14 tools
The eight validate_* tools all live in the same statistical-validation space, and several pairs (deflated vs. haircut Sharpe, overfitting vs. luck trials, track record vs. backtest length) address closely related multiple-testing and luck questions. The descriptions are detailed enough to separate them, but an agent could easily pick the wrong validator without careful reading.
The validate_<thing> prefix is used consistently for the core validators, and get_receipt, verify_receipt, get_key, and audit_backtest follow a clear verb_noun style. service_status and company_financial_history are noun-phrase outliers, so the pattern is not perfectly uniform.
At 14 tools, the set is reasonably scoped for a validation API with distinct statistical checks plus support operations. It is not bloated, though company_financial_history feels tangential to the validation mission, making the count slightly broader than necessary.
The surface covers the main validation lifecycle: multiple-testing corrections, track record, backtest length, paper evidence, breadth, combined audit, receipts, status, and key issuance. There are no obvious dead ends for the stated purpose, and the receipt/key/status tools close the operational loop.