Deptho MCP
Related Servers
Alternatives to Deptho MCP
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI agents to query survivorship-free, point-in-time US market data — universes, OHLCV bars, as-filed fundamentals, macro vintages, COT and 13F holdings — and to run server-side backtests with reproducible run IDs and deflated Sharpe ratios. It connects as a remote Streamable HTTP endpoint or a local stdio process, authenticated via OAuth 2.1 with PKCE or an API key header.11MIT- 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
- AlicenseAqualityAmaintenanceGenerate annotated post-trade candlestick review-chart PNGs from broker or exchange fills. Includes capability checks, no-charge preflight validation, and chart rendering; no signals or order execution.320MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to log trades from chart screenshots, validate them against custom strategy rules, import statements from MT5/TradingView and other brokers, and review R-based statistics in a local dashboard.75 npm1MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first backtesting engine with built-in overfitting detection (PBO, deflated Sharpe, bootstrap CI, walk-forward) and a native MCP server for AI agents to validate trading strategies.4Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and developers to independently verify trading-strategy backtests, detect look-ahead bias, hidden costs, and overfitting, and obtain verdicts with reproducible, optionally signed certificates.143 PyPI9MIT
TDQS
Scored across 5 tools
replay_orders and pro_replay have the same output and both replay an orders CSV, differing mainly by data source and Pro licensing. The distinction is explained, but an agent must reason about prerequisites to choose correctly. The remaining tools (tearsheet, pro_status, pro_sync) are clearly distinct.
Most names use a readable verb_noun or prefixed form (replay_orders, pro_status, pro_sync, pro_replay), with a consistent pro_ prefix for licensed tools. The noun-only tearsheet is a minor deviation but remains clear as a domain term.
Five tools is well-scoped for a backtest replay and reporting server. Each tool has a clear role: replay, reporting, and Pro dataset management.
The surface covers the core workflow: syncing trade data, replaying orders, and generating a tearsheet with headline metrics. Minor gaps exist around inspecting intermediate results or non-Pro dataset management, but agents can work around them.