list_active_signals — VolatiAI MCP MCP Tool Read-only
list_active_signals
(list active signals) is one of 5 tools on the
VolatiAI MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_active_signals from your client
- Claude Code VolatiAI MCP list_active_signals run in your project directory
- Claude Desktop VolatiAI MCP list_active_signals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VolatiAI MCP list_active_signals ~/.cursor/mcp.json
- VS Code VolatiAI MCP list_active_signals .vscode/mcp.json
- Zed VolatiAI MCP list_active_signals ~/.config/zed/settings.json
- Windsurf VolatiAI MCP list_active_signals ~/.codeium/windsurf/mcp_config.json
- Cline VolatiAI MCP list_active_signals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VolatiAI MCP list_active_signals ~/.gemini/settings.json
- Grok VolatiAI MCP list_active_signals .mcp.json (in your project root)
- ChatGPT VolatiAI MCP list_active_signals Settings → Connectors → Advanced → Developer mode
- Claude.ai VolatiAI MCP list_active_signals Settings → Connectors → Add custom connector
- LangChain VolatiAI MCP list_active_signals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http volatiai-mcp https://volatiai-mcp.fourieranalys.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 November 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.