known_at_time_backtest_check — FXMacroData MCP Prompt

known_at_time_backtest_check is one of 15 prompts on the FXMacroData MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke known_at_time_backtest_check from your client

• Claude Code FXMacroData Prompt/known_at_time_backtest_check run in your project directory
• Claude Desktop FXMacroData Prompt/known_at_time_backtest_check ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor FXMacroData Prompt/known_at_time_backtest_check ~/.cursor/mcp.json
• VS Code FXMacroData Prompt/known_at_time_backtest_check .vscode/mcp.json
• Zed FXMacroData Prompt/known_at_time_backtest_check ~/.config/zed/settings.json
• Windsurf FXMacroData Prompt/known_at_time_backtest_check ~/.codeium/windsurf/mcp_config.json
• Cline FXMacroData Prompt/known_at_time_backtest_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI FXMacroData Prompt/known_at_time_backtest_check ~/.gemini/settings.json
• Grok FXMacroData Prompt/known_at_time_backtest_check .mcp.json (in your project root)
• ChatGPT FXMacroData Prompt/known_at_time_backtest_check Settings → Connectors → Advanced → Developer mode
• Claude.ai FXMacroData Prompt/known_at_time_backtest_check Settings → Connectors → Add custom connector
• LangChain FXMacroData Prompt/known_at_time_backtest_check pip install langchain-mcp-adapters

Other prompts on this server

• macro_briefing
• rate_decision_brief
• pair_analysis
• pre_central_bank_decision_brief
• post_release_trade_summary
• pair_risk_check
• week_ahead_macro_plan
• data_quality_audit
• release_risk_ladder
• event_gated_backtest_brief
• portfolio_event_risk_scan
• cot_positioning_context
• commodity_fx_context
• visualize_macro_series

FXMacroData also offers 9 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.