explain_signal — mcp MCP Tool
explain_signal
(explain signal) is one of 26 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explain_signal from your client
- Claude Code mcp explain_signal run in your project directory
- Claude Desktop mcp explain_signal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp explain_signal ~/.cursor/mcp.json
- VS Code mcp explain_signal .vscode/mcp.json
- Zed mcp explain_signal ~/.config/zed/settings.json
- Windsurf mcp explain_signal ~/.codeium/windsurf/mcp_config.json
- Cline mcp explain_signal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp explain_signal ~/.gemini/settings.json
- Grok mcp explain_signal .mcp.json (in your project root)
- ChatGPT mcp explain_signal Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp explain_signal Settings → Connectors → Add custom connector
- LangChain mcp explain_signal pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://quantustik.com/mcpOther tools on this server
- get_signal
- get_trade_plan
- get_signals_batch
- get_forecast
- get_market_regime
- get_risk_state
- get_risk_state_evidence
- get_market_overview
- get_market_indicators
- get_ticker_indicators
- get_fear_greed
- get_signal_history
- get_track_record
- get_earnings_calendar
- scan_universe
- get_correlation_map
- get_insider_pulse
- get_filings_digest
- get_filing_language_diff
- get_institutional_activity
- top_opportunities
- search
- fetch
- list_capabilities
- get_started
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.