risk_check — PreReason MCP Prompt

risk_check is one of 6 prompts on the PreReason MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke risk_check from your client

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

Other prompts on this server

• daily_market_briefing
• mining_profitability
• macro_regime_check
• correlation_scanner
• weekly_recap

PreReason also offers 3 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.