get_risk_state — RiskState — Crypto Risk Engine MCP Tool Read-only
get_risk_state
(get risk state) is one of 3 tools on the
RiskState — Crypto Risk Engine
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_risk_state from your client
- Claude Code RiskState — Crypto Risk Engine get_risk_state run in your project directory
- Claude Desktop RiskState — Crypto Risk Engine get_risk_state ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RiskState — Crypto Risk Engine get_risk_state ~/.cursor/mcp.json
- VS Code RiskState — Crypto Risk Engine get_risk_state .vscode/mcp.json
- Zed RiskState — Crypto Risk Engine get_risk_state ~/.config/zed/settings.json
- Windsurf RiskState — Crypto Risk Engine get_risk_state ~/.codeium/windsurf/mcp_config.json
- Cline RiskState — Crypto Risk Engine get_risk_state ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RiskState — Crypto Risk Engine get_risk_state ~/.gemini/settings.json
- Grok RiskState — Crypto Risk Engine get_risk_state .mcp.json (in your project root)
- ChatGPT RiskState — Crypto Risk Engine get_risk_state Settings → Connectors → Advanced → Developer mode
- Claude.ai RiskState — Crypto Risk Engine get_risk_state Settings → Connectors → Add custom connector
- LangChain RiskState — Crypto Risk Engine get_risk_state pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://api.riskstate.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.