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