flox-mcp
OfficialRelated Servers
Alternatives to flox-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceAI-powered trading toolkit with backtesting, live sentiment, Yahoo Finance data, and 30+ technical analysis tools, integrated as an MCP server for Claude and other AI clients.372,082 PyPI4,605MIT
- AlicenseNot gradedqualityDmaintenanceThe most complete AI-powered trading toolkit for Claude and MCP clients, offering backtesting, live sentiment, Yahoo Finance, and 30+ technical analysis tools in one MCP server.MIT
- AlicenseBqualityBmaintenanceLocal-first MCP server for building and running reproducible Backtrader strategies offline, with tools to inspect datasets, manage drafts, and execute backtests via controlled subprocess runs. It supports multiple hosts including Claude, Codex, OpenCode, and OpenClaw through stdio.301MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes trading analytics — technical indicators, portfolio state, risk metrics, and backtest results — as tools an LLM agent can call.5MIT
- FlicenseNot gradedqualityDmaintenanceFull-lifecycle algorithmic trading MCP server. AI strategy generation from plain English, backtesting, live bot deployment to 10+ brokers, portfolio monitoring, and prediction markets. Stocks, options, crypto, futures. 32 tools. Free tier.-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with financial tools including real-time quotes, backtesting, technical analysis, and multi-exchange data via a simple CLI interface.1MIT
TDQS
Scored across 38 tools
Most tools have clearly distinct purposes, but a few pairs (validate_strategy vs validate_strategy_no_lookahead, replay_window vs whatif, price_amm_swap vs amm_price_impact) could be confused by name alone. The detailed descriptions disambiguate them well, so agents are unlikely to misselect if they read them.
The vast majority of tools follow a verb_noun pattern (list_*, get_*, cancel_*, set_*, run_backtest, etc.), which provides a predictable structure. However, there are a few oddballs like flox_overview, flox_venue_guide, whatif, and amm_price_impact that break the pattern, creating minor inconsistency.
With 38 tools, this server far exceeds the 15-tool sweet spot and even the 25-tool threshold. While the tools cover a wide range of features (discovery, backtesting, live inspection, orders, DEX), the sheer number makes the surface heavy to navigate, though each tool individually has a clear role.
The tool surface covers the major workflows: documentation, strategy scaffolding/validation, backtesting/replay, live engine inspection, order management, and DEX pricing/routing. Minor gaps exist (e.g., no explicit strategy deletion or risk-limit configuration), but agents can work around them with the provided tools like scaffold_strategy and docs_search.