mcpbeat Sign in

Forex-GPT MCP Server

answering

Forex-GPT MCP Server is answering right now. Last checked 14 min ago. It exposes 69 tools.

AI-powered forex and crypto trading analysis with real-time data across 127+ instruments.

Uptime history 47 days of history · worst day 97%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
69
Tools
read from the server
681 ms
Response time
average over 24h
open, no key
Access
sse

What changed 119

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

13 Sep 3 tools changed the parameters they ask for analyze_asset, analyze_timeframes, analyze_watchlist
13 Sep a tool description was rewritten analyze_asset
10 Sep a tool changed the parameters it asks for chart_chat_proxy
8 Sep 5 tools appeared cancel_trailing_stop, get_market_movers, get_performance_summary and 2 more
8 Sep 4 tools changed the parameters they ask for set_trailing_stop, trade_limit_order, trade_market_order and 1 more
8 Sep 3 tools disappeared cancel_trailing_stop, get_trailing_stops, set_trailing_stop
8 Sep 3 tool descriptions were rewritten backtest_run, scan_market, set_trailing_stop
7 Sep 6 tools disappeared _crypto_news_text, get_crypto_news, get_pending_orders and 3 more
7 Sep 5 tools appeared _crypto_news_text, get_crypto_news, get_pending_orders and 2 more
7 Sep 5 tool descriptions were rewritten get_instrument_cache_status, get_instrument_specs, get_market_categories and 2 more
and 83 more, back to 3 September 2026

Forex-GPT MCP Server does not always answer

Over the last week it answered 99.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add forex-gpt-mcp --transport http https://mcp.forex-gpt.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "forex-gpt-mcp": {
      "url": "https://mcp.forex-gpt.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.forex-gpt-mcp]
url = "https://mcp.forex-gpt.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "forex-gpt-mcp": {
      "url": "https://mcp.forex-gpt.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "forex-gpt-mcp": {
      "url": "https://mcp.forex-gpt.ai/mcp"
    }
  }
}

Available tools 69

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent
agent_approve
Approve a pending agent action (trade entry, exit, modification). Args: action_id: The pending action ID to approve adjust_sl: Optional adjusted stop-loss price adjust_tp: Optional adjusted take-profit price adjust_size: Optional adjusted position size (units) Returns: Result of the executed action Example: "Approve action xyz789" or "Approve the pending EUR/USD trade"
agent_history
Get historical performance and actions for an agent. Args: agent_id: Specific agent, or omit for all agents days: Number of days of history (1-90). Default: 7 include_cycles: Include detailed scan cycle logs include_trades: Include trade history. Default: True limit: Max trades per agent (the Pro Terminal dashboard sends this; unknown args previously made the whole call fail) Returns: Historical performance data, trade log, and statistics Example: "Show me my agent's trading history for the past week"
agent_link_telegram
Link your Telegram account to receive agent notifications. To get your Telegram chat ID: 1. Open Telegram and search for @userinfobot 2. Start the bot and it will show your ID 3. Copy the number and use it here Args: telegram_chat_id: Your Telegram chat ID (a number like "123456789") Returns: Confirmation of successful linking Example: "Link my Telegram with chat ID 123456789"
agent_list_strategies
List all available trading strategies with descriptions. Returns information about each strategy including: - Recommended timeframes and instruments - Typical hold times - Risk profile - Minimum scan interval Example: "What trading strategies can the agent use?"
agent_modify
Modify a running agent's parameters. Args: agent_id: The agent ID to modify risk_per_trade: New risk per trade percentage (0.1-5.0) max_positions: New maximum concurrent positions (1-10) control_level: New control level ("manual", "supervised", "semi_auto", "full_auto") scan_interval_minutes: New scan interval in minutes instruments: Replace instrument list entirely add_instruments: Add instruments to existing list remove_instruments: Remove instruments from list custom_rules: Update custom instructions pause: True to pause agent, False to resume min_score: Minimum sentiment score for scan filtering (0-100) sentiment_threshold: (HFT) Minimum abs(score) to trigger signal (50-100) sl_pips: (HFT) Stop loss in pips (1-50) tp_multiplier: (HFT) Take profit multiplier on SL distance (1.0-5.0) exclude_categories: Asset categories to exclude from scanning/trading. Options: "forex", "crypto", "indices", "commodities", "metals", "bonds". Pass empty list [] to clear exclusions. exclude_instruments: List of specific instruments to exclude from trading, e.g. ["USD_TRY", "EUR_TRY"]. Pass empty list [] to clear exclusions. allow_closed_markets: If True, generate signals for closed markets using limit orders instead of market orders. Default: False (skip closed markets). auto_scan: Enable/disable dynamic scanning. When True with empty instruments, agent rescans market each cycle to find fresh opportunities. Returns: Updated agent configuration Example: "Change my agent to 0.5% risk" or "Add GBP/USD to the agent"
agent_notification_settings
View your notification settings and linked accounts. Returns: Your current notification preferences and linked services Example: "Show my notification settings"
agent_reject
Reject a pending agent action. Args: action_id: The pending action ID to reject reason: Optional reason for rejection (helps agent learn) pause_agent: If True, pause the agent after rejection Returns: Confirmation of rejection Example: "Reject that trade, the spread is too high right now"
agent_start
Start an autonomous trading agent with specified strategy. This creates a new agent that will scan markets, analyze opportunities, and trade (or request approval) based on your configuration. Args: strategy: Strategy type - "swing", "scalper", "news_trader", "trend_follower", "breakout", "mean_reversion", "hft" instruments: List of instruments to trade, e.g. ["EUR_USD", "XAU_USD"]. Optional if auto_scan=True. auto_scan: If True, automatically scan market to find high-scoring opportunities. Default: False scan_min_score: Minimum score (0-100) for auto-scanned instruments. Default: 70 scan_limit: Maximum number of instruments from scan results. Default: 10 exclude_instruments: List of instruments to exclude from trading, e.g. ["BTC_USD", "ETH_USD"] timeframes: Timeframes to analyze, e.g. ["H1", "H4", "D"]. Defaults to strategy recommendation. risk_per_trade: Maximum risk per trade as % of account (0.5-5.0). Default: 1.0 max_positions: Maximum concurrent open positions (1-10). Default: 3 control_level: Autonomy level. Options: - "manual": Analysis only, no trading - "supervised": Agent proposes trades, you approve each one - "semi_auto": Auto-execute small trades, approve larger ones - "full_auto": Fully autonomous within risk limits scan_interval_minutes: How often to scan market (5-1440). Default: 60 notifications: Channels for alerts - ["telegram", "email", "push"]. Default: ["telegram"] custom_rules: Optional custom instructions for the agent min_score: Minimum sentiment score for scan filtering (0-100). Overrides strategy default. sentiment_threshold: (HFT) Minimum abs(score) to trigger signal (50-100). Default: 80 sl_pips: (HFT) Stop loss in pips (1-50). Default: 10 tp_multiplier: (HFT) Take profit multiplier on SL distance (1.0-5.0). Default: 1.5 exclude_categories: Asset categories to exclude from scanning/trading. Options: "forex", "crypto", "indices", "commodities", "metals", "bonds". e.g. ["crypto", "bonds"] to skip all crypto and bond instruments. allow_closed_markets: If True, generate signals for closed markets using limit orders (executed when market reopens). Default: False (skip closed markets). cooldown_enabled: If True, enforce cooldown period after trading a pair. Default: True. cooldown_hours: Hours to wait before re-trading same instrument. Default: 4. allow_wide_spreads: If True, trade even when spread is abnormally wide (3x+ typical). Default: False. Useful for exotic pairs with naturally wide spreads. Returns: Agent details including ID, status, and next scan time Examples: "Start a scalper agent, auto-scan for opportunities with score > 80" "Start a swing agent on EUR/USD and Gold, exclude crypto" "Start an HFT agent on EUR/USD with 5 pip stop loss and 2x take profit"
agent_status
Get status of one or all your agents. Args: agent_id: Specific agent ID, or omit for all agents Returns: Agent status including P&L, open positions, pending approvals Example: "What is my agent doing?" or "Show status of agent abc123"
agent_stop
Stop a running agent. Args: agent_id: The agent ID to stop close_positions: If True, close all positions opened by this agent cancel_pending: If True, cancel all pending orders from this agent Returns: Confirmation of agent stop and any actions taken Example: "Stop agent abc123 and close all its positions"
backtest
backtest_history
List recent backtest runs, optionally filtered by instrument. Args: instrument: Filter by instrument (optional) limit: Max results (1-50). Default: 20 Returns: List of recent backtest runs with summary stats Example: "Show my backtest history" or "Show backtests for XAU_USD"
backtest_list_saved
List saved parameter presets, optionally filtered by instrument. Args: instrument: Filter by instrument (optional) Returns: List of saved parameter sets Example: "Show my saved backtest params" or "Show saved params for EUR_USD"
backtest_optimize
Grid search optimization to find the best parameter set for an instrument. Tests all combinations of sentiment_threshold, SL distance, and tp_multiplier and ranks results by the chosen metric. On forex/OANDA the SL grid is sl_pips_range (pips); on Hyperliquid, where pips are meaningless for crypto perps, it is sl_pct_range (% of price). Args: instrument: Instrument (e.g. EUR_USD, XAU_USD; BTC on Hyperliquid) timeframe: Candle granularity. Default: H1 count: Historical candles to fetch (100-5000). Default: 5000 threshold_range: Comma-separated sentiment thresholds to test. Default: "70,75,80,85,90,95" sl_pips_range: Comma-separated SL values in pips (forex). Default: "5,8,10,15,20" tp_mult_range: Comma-separated TP multipliers. Default: "1.0,1.5,2.0,2.5,3.0" rank_by: Metric to rank by: "sharpe", "pnl", "profit_factor", "win_rate". Default: "sharpe" initial_balance: Starting balance. Default: 10000 lookback: Candles lookback for indicators. Default: 120 spread_pips: Estimated spread in pips (forex). Default: 2.0 sl_pct_range: Comma-separated SL values as % of price (Hyperliquid). Default: "0.5,1.0,1.5,2.0,3.0" spread_pct: Estimated spread+slippage as % of price (Hyperliquid). Default: 0.05 Returns: Best parameters and top 50 results ranked by chosen metric Example: "Optimize EUR_USD on H4 and find the best threshold and SL"
backtest_run
Run a backtest on historical data using sentiment-based signals. Uses the same deterministic sentiment scoring as the live scanner (Bollinger Bands + SMA alignment) to generate buy/sell signals when abs(score) >= threshold. Distance mode is automatic: forex/OANDA instruments use pips (sl_pips/spread_pips); on Hyperliquid, where pips are meaningless for crypto perps, SL and spread are a percent of price (sl_pct/spread_pct) and trade "pips" figures are percent moves. Args: instrument: Instrument (e.g. EUR_USD, XAU_USD; BTC on Hyperliquid) timeframe: Candle granularity — M1, M5, M15, M30, H1, H2, H4, H6, H8, H12, D or W (aliases like 1h/4h/daily accepted; monthly is not available). Default: H1 count: Number of historical candles (100-5000). Default: 5000 sentiment_threshold: Minimum abs(score) to trigger signal (50-100). Default: 80 sl_pips: Stop loss in pips (forex). Default: 10 tp_multiplier: Take profit as multiple of SL. Default: 1.5 risk_per_trade: Risk per trade as % of balance. Default: 1.0 max_positions: Max concurrent positions. Default: 1 spread_pips: Estimated spread in pips (forex). Default: 2.0 lookback: Candles lookback for indicators. Default: 120 initial_balance: Starting balance for simulation. Default: 10000 sl_pct: Stop loss as % of price (Hyperliquid/crypto). Default: 1.0 spread_pct: Estimated spread+slippage as % of price (Hyperliquid). Default: 0.05 Returns: Backtest results with stats, equity curve, and trade list Example: "Backtest EUR_USD on H4 with 90 threshold"
backtest_save_params
Save a backtest's parameters as a reusable preset. Args: backtest_id: The backtest run ID to save params from name: Name for this parameter set (e.g. "EUR_USD H4 aggressive") Returns: Saved parameter set details Example: "Save those backtest params as 'EUR_USD H4 optimal'"
trade
get_trade_details
Get full details of a specific trade (Open or Closed). Useful to investigate a trade that disappeared or to see its full history.
trade_limit_order
Place a Limit Order. price: The limit price to trigger the order. take_profit: ABSOLUTE PRICE (e.g. 1.1250). stop_loss: ABSOLUTE PRICE (e.g. 1.1100). take_profit_distance: RELATIVE PIPS (e.g. 0.0050). stop_loss_distance: RELATIVE PIPS (e.g. 0.0020). trailing_stop_distance: RELATIVE DISTANCE for trailing stop. guaranteed_stop_loss: True for GSLO. expiry: ISO 8601 string (e.g. "2023-12-31T23:59:00Z"). Defaults to GTC if omitted. client_nonce: Optional. 32-char hex idempotency token. reduce_only: HL only. Order may only close existing position size. tif: HL only. "Gtc" (default), "Alo" (post-only), or "Ioc". payment_proof: Optional. HL mainnet only — pass {"confirmed": true} to acknowledge orders whose notional exceeds HYPERLIQUID_MAINNET_CONFIRM_USD ($500 default).
trade_market_order
Place a Market Order. units: Positive for Buy, Negative for Sell take_profit: ABSOLUTE PRICE (e.g. 1.1250). stop_loss: ABSOLUTE PRICE (e.g. 1.1100). take_profit_distance: RELATIVE PIPS (e.g. 0.0050). Use this OR absolute price. stop_loss_distance: RELATIVE PIPS (e.g. 0.0020). Use this OR absolute price. trailing_stop_distance: RELATIVE DISTANCE for trailing stop (e.g. 0.0020). guaranteed_stop_loss: True to use GSLO (Premium, requires specific SL distance rule). slippage: Hyperliquid-only — fraction (0–0.5) capping IOC price band. Ignored by OANDA/eToro. client_nonce: Optional. 32-char hex idempotency token. Pass the same value from a prior call's response.client_nonce to retry the exact same order without risking a duplicate fill. Server mints one if absent. payment_proof: Optional. HL mainnet only — pass {"confirmed": true} to acknowledge orders whose notional exceeds HYPERLIQUID_MAINNET_CONFIRM_USD ($500 default). UI shows a confirmation modal first, then re-fires with this set.
trade_modify_trade
Modify an existing trade's Stop Loss and Take Profit. You can use absolute prices OR relative distances. Only provided fields will be updated. Args: trade_id: The ID of the open trade to modify. take_profit: New ABSOLUTE price. stop_loss: New ABSOLUTE price. take_profit_distance: New RELATIVE distance (e.g. 0.0050). stop_loss_distance: New RELATIVE distance (e.g. 0.0020).
trade_stop_order
Place a Stop Order (Momentum/Breakout Entry). Use this to Buy ABOVE market price or Sell BELOW market price. Args: instrument: Asset symbol (e.g. 'EUR_USD') units: Positive for Buy, Negative for Sell price: The STOP price to trigger the order. expiry: ISO 8601 string (e.g. "2023-12-31T23:59:00Z"). Defaults to GTC if omitted. take_profit: ABSOLUTE PRICE. stop_loss: ABSOLUTE PRICE. take_profit_distance: RELATIVE DISTANCE (e.g. 0.0050). stop_loss_distance: RELATIVE DISTANCE (e.g. 0.0020). trailing_stop_distance: RELATIVE DISTANCE for trailing stop. guaranteed_stop_loss: True for GSLO. client_nonce: Optional. 32-char hex idempotency token. Pass the same value from a prior call's response.client_nonce to retry without risking a duplicate order. Server mints one if absent.
market
get_market_categories
no description provided
get_market_hours
no description provided
get_market_movers
Top gainers, top losers and (Hyperliquid) top 24h volume across the active broker's whole universe, ranked by daily price change. No Sentiment Score is computed and no tokens are charged — use scan_market for score rankings. Hyperliquid: rolling 24h change from the exchange's own reference price, plus 24h notional volume. OANDA: current daily candle vs the prior close. Args: limit: rows per list (1-50, default 25). liquid_only: Hyperliquid only — rank gainers/losers within the 100 most-traded markets by 24h notional so thin markets don't dominate. timeframe: OANDA only — candle granularity for the change (default "D").
is_market_open
no description provided
analyze
analyze_asset
Run a one-shot technical analysis for a SINGLE asset on a SINGLE timeframe. Use this when the user asks about ONE specific asset by name, e.g.: - "analyze EUR_USD" - "give me your read on BTC on the 4-hour" - "what's the signal on gold?" - "deep analysis on SOL/USDC daily" For multi-asset surveys ("scan the market", "find opportunities", "what looks bullish today") use scan_market INSTEAD — that scans the full universe and returns top setups by sentiment score. Calling analyze_asset for a market-scan query is incorrect and wastes tokens; the user wants a ranked list, not a deep dive on one asset they didn't even name. Args: asset: Asset symbol (e.g., EUR_USD, XAU_USD, BTC, ETH) timeframe: Timeframe for analysis (D, H4, H1, M30, M15, M5, M1) priceType: Price type - B (bid), A (ask), or M (mid) timeoutSec: Timeout in seconds (5-120) language: Optional. The language for the written analysis and the spoken narration — "es", "pt", "zh", "ja". Omit it and nothing changes: the prose follows the language stored on the user's profile, which is what every existing client gets today. Pass it and it wins, because the caller knows what is on screen now while a stored preference read from another process can be a cache interval behind. Numbers, instrument symbols and every structured field stay English either way. Returns: Analysis results with status, signals, and recommendations
analyze_timeframes
Analyze a single asset across multiple timeframes simultaneously. Args: asset: Asset symbol (e.g., EUR_USD) timeframes: List of timeframes (e.g., ["D", "H4", "H1"]) priceType: B (bid), A (ask), or M (mid) timeoutSec: Overall timeout in seconds (30-300) Returns: Multi-timeframe analysis results
analyze_watchlist
Analyze multiple assets from the user's SAVED watchlist in parallel. Args: timeframe: Timeframe (D, H4, H1, etc.) priceType: B (bid), A (ask), or M (mid) timeoutSec: Overall timeout in seconds (30-300) (optional) timeframes: list of timeframes (timeframes mode) – if provided, supersedes timeframe (optional) max_assets: limit how many watchlist assets to analyze (default: all) Returns: Results for all watchlist assets with analysis data
chart
chart_chat_proxy
Proxy to the Flask /api/chart-chat endpoint using the caller's bearer token. Keeps token accounting/auth consistent with the web app while exposing chat via MCP.
get_chart_data
Retrieve OHLC (candlestick) data for charting. Args: asset: Asset symbol (e.g., EUR_USD) timeframe: Timeframe (D, H4, H1, etc.) count: Number of candles (50-5000) Returns: Candlestick data with timestamps, open, high, low, close prices
close
close_position
Close position for an instrument.
close_trade
Close a specific trade (fully or partially).
instrument
get_instrument_cache_status
no description provided
get_instrument_specs
no description provided
open
get_open_positions
List open positions (Net Exposure per instrument). Useful to see total Long/Short units and P&L per pair.
get_open_trades
List open trades.
purchase
purchase_tokens_x402
Purchase premium tokens via X402 crypto payment. Pay $20 USDC to receive 500,000 premium tokens (non-expiring). These tokens can be used to access all ForexGPT tools and services. Args: payment_proof: X402 payment proof containing signature and payment details. Must include: amount, token, network, nonce, v, r, s, from, to, validAfter, validBefore Returns: Success message with new token balance or payment required error. Example payment_proof: { "type": "eip3009", "amount": "20000000", # $20 USDC (6 decimals) "token": "USDC", "network": "eip155:84532", # Base Sepolia "from": "0x...", # User's wallet "to": "0x...", # Recipient (ForexGPT treasury) "nonce": "0x...", "validAfter": 1234567890, "validBefore": 1234567890, "v": 27, "r": "0x...", "s": "0x..." }
purchase_tokens_x402_solana
Purchase premium tokens via X402 payment on Solana. Pay $20 USDC on Solana (devnet or mainnet) to receive 500,000 premium tokens. Credits go to the same purchased_tokens balance used by the Stripe and EVM rails — one balance, three rails. Two accepted proof shapes: signed_authorization (off-chain Ed25519 sig over a canonical message): { "type": "signed_authorization", "network": "solana:devnet", "token": "USDC", "from": "<signer pubkey base58>", "to": "<treasury pubkey base58>", "amount": "20000000", "nonce": "<random hex>", "valid_before": <unix seconds>, "signature": "<base58 ed25519 signature>" } settled_tx (confirmed SPL USDC transfer, fetched and diffed via RPC): { "type": "settled_tx", "network": "solana:devnet", "token": "USDC", "from": "<signer pubkey base58>", "to": "<treasury pubkey base58>", "amount": "20000000", "nonce": "<idempotency key>", "tx_signature": "<base58 transaction signature>" }
save
save_broker_credentials
Save broker credentials. Supports multiple brokers. Args: broker: The broker name - "oanda", "etoro", or "hyperliquid" api_key: Your broker API key (OANDA/eToro). NOT used for Hyperliquid (see below). account_id: Your broker account ID (required for OANDA) user_key: Your eToro user key (required for eToro) demo_mode: Use demo/virtual portfolio (eToro only, default True) Note for Hyperliquid users: Hyperliquid does not use API keys. Instead you connect a self-custody Web3 wallet and authorize a trading agent via an on-chain EIP-712 signature. This MCP tool cannot perform that signature — it requires a wallet popup in the FE. Calling this tool with broker="hyperliquid" returns instructions instead of saving anything. Use the FE flow at Settings → Hyperliquid → "Connect Wallet" + "Authorize Trading".
save_oanda_credentials
Save your OANDA API Key and Account ID securely. These are required before you can trade.
watchlist
add_to_watchlist
Add a new asset to your persistent watchlist. Args: asset: Asset symbol (e.g. 'EUR_USD', 'BTC_USD')
get_watchlist
View the assets the user has SAVED to their persistent watchlist. Use this when the user asks about their watchlist, e.g.: - "show my watchlist" - "what's on my watchlist" - "list my watchlist" - "what assets am I watching" This is NOT the same as open positions / trades. The watchlist is a saved list of asset SYMBOLS the user follows; it has no balance, P&L, units, or entry-price data. For open positions use get_open_positions; for open trades use get_open_trades. Do NOT call get_open_positions or get_open_trades for watchlist queries — you'd return position data that doesn't match what the user asked. Returns: {count, assets, status} — list of saved asset symbols and count.
x402
x402_evm_config
Return the public EVM x402 config: recipient address, supported networks (CAIP-2 keys → USDC contract + RPC URL + chain name), and the token package. Pairs with x402_solana_config so the WalletPaymentModal can render a Solana | EVM tab switcher and let the user pay from whichever wallet they have. No auth — every value is broadcast on-chain at payment time anyway.
x402_solana_config
Return the public Solana x402 config: recipient pubkey, supported networks (with USDC mints + RPC URLs), and the token package. No authentication required — every value here is broadcast publicly on-chain at payment time anyway. The frontend calls this on the payment modal's mount so the build doesn't need its own VITE_SOLANA_* env vars; one source of truth lives on the MCP container.
account
get_account_history
Get account transaction history (e.g. closed trades, order fills). Useful for finding past trades, reporting, or auditing. Args: from_time: Start time (RFC3339 format, e.g. "2023-05-01T00:00:00Z"). to_time: End time (RFC3339). type_filter: Comma-separated types (e.g. "ORDER_FILL,TRADE_CLOSE"). To see closed trades, use "TRADE_CLOSE".
assets
list_assets
Return supported asset symbols for the active broker. For OANDA containers: returns the OANDA universe (~120 instruments). For Hyperliquid containers: returns the Hyperliquid perp universe (~230 markets) with per-asset metadata (current price, max leverage, funding rate, open interest, 24h volume, product_type, sector, is_pre_launch, is_hip3). When ``include_spot=True`` (default), the spot universe from ``/info{spotMeta}`` is appended — instruments tagged ``product_type="spot"`` use ``_USDC`` suffix so they don't collide with perp canonical names. Optional: • filter: substring (case-insensitive) to narrow the list • asset: specific symbol to test membership • include_spot: append HL spot markets (HL only; default True)
blog
get_blog_articles
Get recent articles from the Forex-GPT blog feed. Args: max_results: Maximum number of articles to return (1-50, default: 10) category: Optional category slug to filter by. When unset, the tool falls back to a broker-aware default: - hyperliquid containers → "daily-crypto-hype" (ID 24) so HL users see only crypto-focused content, not the forex daily AI analysis stream. - Anything else → site-wide feed. Pass an explicit slug (e.g. "daily-deep-dive", "the-weekly-open") to override the default. Returns: List of recent blog articles with titles, URLs, summaries, images, and publication dates
cancel
cancel_pending_order
Cancel a pending (unfilled) Limit or Stop order. Args: order_id: The OANDA ID of the order to cancel.
crypto
get_crypto_news
Aggregated crypto-news feed from quality free RSS sources (CoinDesk, Decrypt, Blockworks, The Defiant). Sorted newest-first, deduped by URL across sources. Args: max_results: 1-50, default 25. ticker: Optional symbol filter (e.g. "BTC", "ETH", "SOL", "HYPE"). When set, only articles mentioning the ticker (case-insensitive substring match in title OR summary) are returned. Pass "all" or empty to disable filtering. Returns: {status, count, ticker, articles: [{title, url, summary, published, source, image?}]}
economic
economic_events
Fetch upcoming economic events via the TradingView proxy source. Args: fromDays: Start of date range (days from now, 0-90) toDays: End of date range (days from now, 0-90) Returns: List of economic events with importance, country, and timing
fetch
fetch
Retrieve complete forex analysis by ID. Args: id: Analysis ID in format "ASSET_TIMEFRAME" (e.g., "EUR_USD_D", "XAU_USD_H4") Returns: Full analysis document with technical indicators, signals, and recommendations
from
remove_from_watchlist
Remove an asset from your persistent watchlist. Args: asset: Asset symbol to remove
health
health
Comprehensive health and status check including optional upstream dependencies. Args: checkOpenAI: Verify OpenAI API connectivity checkTradingView: Verify TradingView API connectivity checkOANDA: Verify OANDA API connectivity Returns: Health status with environment info and dependency checks
help
help_tutorial
Master tutorial for MCP tools: usage tips, key parameters, and suggested flows.
live
get_live_heatmap
Generates a real-time Sentiment Heatmap snapshot. Behavior: 1. If 'assets' are provided, scans those specific assets. 2. If 'assets' not provided, scans the user's saved Watchlist. 3. If Watchlist is empty, scans a default list of popular global assets. Args: assets: Optional list of symbols. timeframe: Granularity (e.g. 'H1', 'D').
oanda
delete_oanda_credentials
Remove/Delete your stored OANDA API Key and Account ID. Use this if you want to clear your credentials or switch accounts.
order
get_order_history
Get OANDA order history (FILLED, CANCELLED, TRIGGERED, etc.). state: "ALL", "PENDING", "FILLED", "TRIGGERED", "CANCELLED". count: Max 500.
pending
get_pending_orders
List all PENDING orders (Limits, Stops, Entry Orders). These are orders waiting to be filled.
performance
get_performance_summary
Trading-performance aggregates: realized P&L net of fees, total fees paid, perp funding paid/received, fill count, plus a daily breakdown for the chart. Args: window: "7d" | "30d" | "90d" | "ytd" | "all" (default). Filters fills + funding by their HL timestamp. Lifetime totals are always returned alongside the windowed slice.
price
get_price_stream_url
Return a short-lived URL for the raw price stream (SSE) for given instruments. The URL expires after ~10 minutes.
refresh
refresh_instrument_data
Manually refresh instrument data from OANDA API. Updates financing rates, margin requirements, and other parameters. Requires: User must have saved OANDA credentials via save_oanda_credentials. Returns: - success: Boolean indicating if refresh succeeded - message: Status message - count: Number of instruments refreshed - refreshedAt: Timestamp of refresh Note: This fetches fresh data from OANDA's practice environment. The cache is automatically refreshed on server startup if data is >24 hours old.
replace
replace_pending_order
Replace (Modify) an existing pending order. Basically cancels the old one and places a new one atomically. Args: order_id: ID of the order to replace. type: 'LIMIT' or 'STOP'. client_nonce: Optional. 32-char hex idempotency token for the new order. Pass the same value from a prior call's response to retry safely. Server mints one if absent. (All other args same as placement tools)
research
research_briefing
Generate a short AI briefing (one paragraph + three bullets) from the terminal's current research context: watchlist Sentiment Scores, running agents and their theses, open positions, upcoming events / headlines and the latest research article. Charged to the user's tokens like any AI analysis (1 token = 1 LLM token); refused when the balance can't cover it. Args: context: JSON assembled by the terminal — keys: pulse, agents, positions, events, headlines, article, network, broker.
scan
scan_market
Scans the FULL market universe (Forex, Crypto, Metals, Indices) and returns the top trading opportunities ranked by sentiment score. Use this when the user asks for a MULTI-ASSET survey or anything that implies scanning / finding opportunities across the market. Example user phrasings that should trigger scan_market: - "scan the market" - "scan market on daily for score of 85" - "what's bullish on the H4?" - "find me strong setups" - "show top opportunities" - "what looks bearish right now?" - "any crypto setups?" For deep analysis of a SINGLE specific asset the user names by symbol, use analyze_asset instead. Do NOT call analyze_asset on a single asset when the user asked for a scan — that produces one deep dive instead of the ranked list they wanted. Common arg parsing from user phrasings: - "score of 85" / "min score 85" / "score >= 85" → min_score=85 - "on daily" / "on D" / "1d" → timeframes=["D"] - "on 4-hour" / "H4" / "4h" → timeframes=["H4"] - "top 10" / "top 5" → limit=10 / limit=5 - "bullish only" → sentiment="bullish" - "crypto" / "stocks" → include_categories=["crypto"] / ["stocks"] Args: timeframes: List of timeframes to scan (e.g. ["H1", "H4", "D"]). Default is ["H8"]. min_score: Minimum absolute sentiment score (0-100) to include. Default 80 (Bullish/Bearish). limit: Maximum number of results to return. Default 6. include_categories: Optional list of category names to keep. Each name matches the engine's `sector` (crypto/stocks/indices/commodities/fx) OR `product_type` (perp/spot) OR special tokens "hip3"/"pre-launch". Case-insensitive. Empty/None = include everything. exclude_categories: Optional list of category names to exclude. Applied AFTER include filter. Same vocabulary. universe_scope: "top25" (default; rank by 24h volume then keep top 25) or "all" (the 100 most-traded markets by 24h volume — a hard cap that keeps scan time and the shared exchange rate budget bounded; it is NOT the whole ~500-market universe). HL only — OANDA always uses its static universe regardless. min_volume_24h: Drop markets whose volume_24h is below this floor. HL only; OANDA universe has no volume metadata to filter on. Returns: A list of the top opportunities ranked by sentiment strength.
search
search
Search forex analysis results by asset name, timeframe, or keywords. Returns a list of available analyses matching the search criteria. Args: query: Search query (e.g., "EUR_USD", "daily analysis", "gold", "bitcoin") Returns: Search results with IDs for fetching full analysis
sentiment
get_sentiment_stream_url
Return a short-lived URL for the sentiment stream (SSE) for given instruments and granularity. The URL expires after ~10 minutes.
server
get_server_time
Return the server's current UTC timestamp (ISO 8601).
spreads
get_spreads
Checks the current liquidity and trading cost (spread) for an asset. Useful for checking if a market is too expensive to trade right now. Args: asset: The asset symbol (e.g., "EUR_USD", "XAU_USD") Returns: Current spread, average spread, and cost in basis points.
token
get_token_balances
Return the current user's token balances from Auth0 app_metadata. Uses _safe_profile() so that the same values shown inside AI analysis (token_quota, purchased_tokens, total_token_usage, last_reset, email, user_id) are returned in a simple JSON structure.
trading
get_trading_account
Get trading account summary (balance, margin).

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

_crypto_news_text
removed 7 Sep 2026
_order_line_fields
removed 7 Sep 2026
trade_update_leverage
removed 7 Sep 2026
cancel_trailing_stop
removed 8 Sep 2026
get_trailing_stops
removed 8 Sep 2026
set_trailing_stop
removed 8 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://mcp.forex-gpt.ai/mcp sse answering 443 ms 14 min ago

Alternatives to Forex-GPT MCP Server

same job, measured the same way
Cryptopolitan MCP
by 4dmrkey

Real-time crypto news, analysis, and price predictions for AI agents via MCP.

5 tools answering
Cryptodata MCP
by kota1026

CryptoData MCP Server - Real-time crypto market data, DeFi analytics, and on-chain intelligence...

28 installs/wk local only
Tradingview MCP
by atilaahmettaner

Real-time market data, screeners, technical analysis & backtesting for stocks, crypto and forex.

answering
eToro MCP Server
by gabrielcerutti

Connect AI assistants to eToro for portfolio analysis, market research, and trading.

74 installs/wk local only
Traderwai
by traderwai

AI-powered charts with indicators and trade execution for forex, gold, indices & crypto.

answering
Mudrex MCP Server
by mudrex

MCP server for Mudrex futures trading enabling AI agents to securely access data and risk tools.

answering
Webull OpenAPI
by webull-inc

MCP server for Webull OpenAPI: trading and market data access for AI assistants

554 installs/wk local only
Gloria AI
by jchen225

Real-time curated crypto news for AI agents with sentiment, recaps, and search.

7 tools answering

Forex-GPT MCP Server — questions

Answers built from our own checks of this server.

What can Forex-GPT MCP Server do?
It exposes 69 tools, read directly from the server on our last check. Among them: add_to_watchlist, agent_approve, agent_history, agent_link_telegram, agent_list_strategies, agent_modify and 63 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Forex-GPT MCP Server mostly used for?
Its tools cluster around agent, backtest and trade. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Forex-GPT MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 681 ms. The bar chart above shows every period we have measured.
Did Forex-GPT MCP Server ever remove tools?
Yes. _crypto_news_text, _order_line_fields, trade_update_leverage, cancel_trailing_stop and 2 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Forex-GPT MCP Server?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Forex-GPT MCP Server need an API key?
No. Forex-GPT MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 69 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Forex-GPT MCP Server?
It answers our handshake in 681 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.