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