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