MCP server for AiDataTaskRunner Panel (MT5) - Control data generation and ML model training via MCP
Control AiDataTaskRunner Panel directly via MCP Control your backtesting queue directly from Claude: Add Tasks: Queue new backtests with custom symbols, dates, and timeframes Monitor Status: Track task progress (Processing, Queued, Pending, Ready, Failed) Batch Operations: Execute all pending tasks or clean completed ones File Management: Save/load task configurations from CSV files Manage panel…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Control AiDataTaskRunner Panel directly via MCP Control your backtesting queue directly from Claude: Add Tasks: Queue new backtests with custom symbols, dates, and timeframes Monitor Status: Track task progress (Processing, Queued, Pending, Ready, Failed) Batch Operations: Execute all pending tasks or clean completed ones File Management: Save/load task configurations from CSV files Manage panel settings via Claude: Load/Save Configurations: Save and load panel settings from text files Query…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.