janorium-mcp
OfficialRelated Servers
Alternatives to janorium-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceBacktest PineScript v6 strategies locally from your AI agent: transpiles Pine to C++ and runs it on the deterministic, TradingView-validated PineForge engine via Docker. Tools for single backtests, parameter-grid sweeps, and Binance OHLCV fetch — no API key, data never leaves your machine.1250 npm9MIT
- AlicenseNot gradedqualityCmaintenanceProvides 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.2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables natural language management of Binance USDS-margin futures trading, including balance checks, order placement, stop-loss/take-profit, and strategy backtesting.-

panther-mcpofficial
AlicenseAqualityDmaintenanceEnables AI assistants to backtest trading strategies described in plain English, providing access to market data, technical indicators, and comprehensive performance reports.131MIT- AlicenseNot gradedqualityDmaintenanceProvides real-time cryptocurrency trading signals and technical analysis via Binance, supporting multiple timeframes and indicators.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously analyze market data, compute risk metrics, and execute spot or futures trades on Binance with safety guardrails like dry-run mode and slippage protection.1MIT
TDQS
Scored across 28 tools
Most tools map to a clearly distinct resource and action: strategy lifecycle, backtest analytics, optimization, campaigns, and market data are cleanly separated. The few soft overlaps are research_scan vs research_job_create and generic wait vs the *_get tools, but the descriptions give enough guidance to choose correctly.
The set uses consistent snake_case with a domain/resource prefix followed by an action (strategy_*, backtest_*, optimization_*, campaign_*). Minor deviations such as the bare wait and the longer strategy_set_visibility are still readable and predictable.
At 28 tools the surface exceeds the 25+ threshold for a heavy toolset, even though each tool covers a real operation. The domain is broad, but the set would benefit from consolidation of repeated status/analytics patterns or grouping of related backtest diagnostics.
Core workflows are covered end-to-end: research, strategy validation/save, backtesting, optimization, campaign holdout, and market coverage. However, there are no listing/search tools for strategies, backtests, optimizations, or research jobs, and no strategy delete operation, so agents often need externally supplied IDs. Referenced docs:// resources are also not exposed as callable tools.