get_signal_taxonomy — BounceWatch Signal Intelligence MCP Tool Read-only
get_signal_taxonomy
(get signal taxonomy) is one of 10 tools on the
BounceWatch Signal Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_signal_taxonomy from your client
- Claude Code BounceWatch Signal Intelligence get_signal_taxonomy run in your project directory
- Claude Desktop BounceWatch Signal Intelligence get_signal_taxonomy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BounceWatch Signal Intelligence get_signal_taxonomy ~/.cursor/mcp.json
- VS Code BounceWatch Signal Intelligence get_signal_taxonomy .vscode/mcp.json
- Zed BounceWatch Signal Intelligence get_signal_taxonomy ~/.config/zed/settings.json
- Windsurf BounceWatch Signal Intelligence get_signal_taxonomy ~/.codeium/windsurf/mcp_config.json
- Cline BounceWatch Signal Intelligence get_signal_taxonomy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BounceWatch Signal Intelligence get_signal_taxonomy ~/.gemini/settings.json
- Grok BounceWatch Signal Intelligence get_signal_taxonomy .mcp.json (in your project root)
- ChatGPT BounceWatch Signal Intelligence get_signal_taxonomy Settings → Connectors → Advanced → Developer mode
- Claude.ai BounceWatch Signal Intelligence get_signal_taxonomy Settings → Connectors → Add custom connector
- LangChain BounceWatch Signal Intelligence get_signal_taxonomy pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http signals https://api.bouncewatch.com/api/v1/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.