What problem does it solve? When mem0 memory operations fail, searches return empty results, or MCP connections drop, developers lack a systematic way to pinpoint whether the issue is the API key, identity resolution, connectivity, or write capability. ## Core Features & Use Cases - Five-Point Diagnostic: Checks API key configuration, identity resolution (user/project/branch), MCP server connectivity, memory write/read capability, and session stats tracking in one pass. - Deep Quality Scan: With the --deep flag, detects duplicate, stale, low-confidence, contradictory, and untagged memories across your mem0 store. - Use Case: After add_memory calls start erroring in a coding session, run the health check to get a PASS/FAIL summary per component plus targeted troubleshooting steps for each failure. ## Quick Start Ask the assistant to run the mem0 health check to diagnose why memory operations are failing.