Wraps the ReadyTrader-FOREX MCP server to give agents access to forex market data, economic calendars, technical analysis, and trading.
This server has critical structural issues that severely limit its quality. It is a proxy/wrapper around an external MCP server (ReadyTrader-FOREX) rather than a native MCP implementation. The tools are defined in a custom Agent Zero framework, not as proper MCP tool definitions. Input schemas are visible and properly typed, but descriptions are generic and lack LLM-optimization. Most critically, this is a plugin for Agent Zero (a non-standard agent framework), not a standalone MCP server that can be evaluated against MCP standards. The HTTP transport is a proxy call to localhost:8000, assuming an external MCP server exists. No output schemas are documented. Error handling is minimal, all exceptions are caught and returned as plain text responses without guidance on recovery or root cause.
Fetch OHLCV candle data for a forex pair.
Fetch upcoming economic events that may affect forex markets.
Get a market brief for a specific forex pair.
Fetch the current price of a forex currency pair.
Detect the current market regime for a forex pair.
Get market sentiment for forex pairs from news and social sources.
Run a backtest simulation on a forex strategy.
No output/return schemas documented. Tools return JSON responses with unknown structure. LLMs cannot plan downstream calls or extract specific fields.
GetEconomicCalendar and GetForexSentiment have empty input schemas ({}). No parameters means no context can be passed. LLMs cannot filter results, select timeframes, or narrow scope.
Descriptions are generic and under 50 characters. 'Get market sentiment for forex pairs from news and social sources.' does not explain WHEN to call this, WHAT data it returns, or HOW it differs from GetForexMarketBrief.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 0 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 47 | - | v1 |
Parameter descriptions are minimal or missing context. 'Currency pair symbol (e.g., EURUSD)' includes example value in description, which LLMs tend to reuse literally. Should use enum constraint instead.
Error handling is catch-all with generic messages. No recovery guidance, no retryable classification, no indication of what went wrong. 'Error fetching price: <exception>' gives LLMs nothing actionable.
This is a custom Agent Zero plugin, not a native MCP server. Tool definitions are in a proprietary framework (python.helpers.tool.Tool), not registered as MCP tools. Cannot be validated as an MCP-compliant server.
No pagination support. Tools like GetEconomicCalendar and GetForexSentiment return unbounded results, risking context window exhaustion. No limit, offset, or cursor parameters.
FetchForexOHLCV accepts 'timeframe' as free-form string. Should declare valid timeframes as enum (e.g., 1m, 5m, 15m, 1h, 4h, 1d) to prevent hallucinated invalid values.
RunForexBacktest requires 'strategy_code' as string with no validation or format guidance. No schema, no language spec, no error recovery. This is a high-risk tool for code injection.