assess_situation — Rubin Exchange MCP Prompt

assess_situation is one of 12 prompts on the Rubin Exchange MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke assess_situation from your client

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

Other prompts on this server

• check_portfolio
• scan_markets
• protect_positions
• enter_trade
• flatten_all
• my_rank
• my_fees
• referral_program
• fund_account
• my_account
• latest_news

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.