robustness_review — Backtest360 MCP Prompt

robustness_review is one of 2 prompts on the Backtest360 MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke robustness_review from your client

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

Other prompts on this server

• build_and_validate

Backtest360 also offers 1 resource — 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.