get_news_reaction_speed — OneQAZ Trading Intelligence MCP Resource
get_news_reaction_speed
is one of 17 resources on the
OneQAZ Trading Intelligence
MCP server. Connect the server and your client can attach it as context.
by client
How to attach get_news_reaction_speed from your client
- Claude Code OneQAZ Trading Intelligence Resource/get_news_reaction_speed run in your project directory
- Claude Desktop OneQAZ Trading Intelligence Resource/get_news_reaction_speed ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OneQAZ Trading Intelligence Resource/get_news_reaction_speed ~/.cursor/mcp.json
- VS Code OneQAZ Trading Intelligence Resource/get_news_reaction_speed .vscode/mcp.json
- Zed OneQAZ Trading Intelligence Resource/get_news_reaction_speed ~/.config/zed/settings.json
- Windsurf OneQAZ Trading Intelligence Resource/get_news_reaction_speed ~/.codeium/windsurf/mcp_config.json
- Cline OneQAZ Trading Intelligence Resource/get_news_reaction_speed ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OneQAZ Trading Intelligence Resource/get_news_reaction_speed ~/.gemini/settings.json
- Grok OneQAZ Trading Intelligence Resource/get_news_reaction_speed .mcp.json (in your project root)
- ChatGPT OneQAZ Trading Intelligence Resource/get_news_reaction_speed Settings → Connectors → Advanced → Developer mode
- Claude.ai OneQAZ Trading Intelligence Resource/get_news_reaction_speed Settings → Connectors → Add custom connector
- LangChain OneQAZ Trading Intelligence Resource/get_news_reaction_speed pip install langchain-mcp-adapters
Other resources on this server
- health_check
- server_info
- pg_pool_stats_resource
- get_tool_chains_meta
- discovery_manifest
- get_global_regime_summary
- list_categories
- get_all_markets_summary
- get_all_structures
- get_fear_greed
- get_market_regime
- get_market_context
- get_macro_events
- get_cross_market_correlations
- get_event_leading_scores
- get_cross_market_decoupling
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, 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 resource's type and contents.