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