get_etf_risk — Bullrun MCP Tool Read-only
get_etf_risk
(get etf risk) is one of 30 tools on the
Bullrun
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_etf_risk from your client
- Claude Code Bullrun get_etf_risk run in your project directory
- Claude Desktop Bullrun get_etf_risk ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bullrun get_etf_risk ~/.cursor/mcp.json
- VS Code Bullrun get_etf_risk .vscode/mcp.json
- Zed Bullrun get_etf_risk ~/.config/zed/settings.json
- Windsurf Bullrun get_etf_risk ~/.codeium/windsurf/mcp_config.json
- Cline Bullrun get_etf_risk ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bullrun get_etf_risk ~/.gemini/settings.json
- Grok Bullrun get_etf_risk .mcp.json (in your project root)
- ChatGPT Bullrun get_etf_risk Settings → Connectors → Advanced → Developer mode
- Claude.ai Bullrun get_etf_risk Settings → Connectors → Add custom connector
- LangChain Bullrun get_etf_risk pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bullrun https://mcp.bull-run.org/mcpOther tools on this server
- screen_stocks
- search_etfs
- screen_etfs
- get_etf_index_group
- get_etf_fund
- get_etf_filter_options
- get_etf_snapshot
- get_etf_holdings
- get_etf_timeseries
- get_etf_exposures
- compare_etfs
- analyze_etf_overlap
- analyze_portfolio_fit
- simulate_etf_cost
- query_etfs
- get_stock_metrics
- get_financial_history
- get_quality_moat_metrics
- get_forward_estimates
- get_operating_kpis
- get_revenue_breakdown
- get_earnings_call_transcript
- list_portfolios
- get_portfolio_context
- get_portfolio_analytics
- create_portfolio_draft
- create_position_draft
- create_portfolio_from_positions
- get_capabilities
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.