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