What problem does it solve? Investigating a live AiRaccoon memory server is error-prone: the data root is hidden, MCP responses arrive as SSE frames, settings state is invisible, and sqlite reads of vec0 shadow tables are easy to misinterpret. This Skill captures the exact mechanics for health-checking, querying, and safely inspecting a running server without disturbing the user's instance. ## Core Features & Use Cases - Live server discovery: Locate the data root, bearer token, and bound port of a running ai-raccoon process using pgrep, lsof, and server logs. - Health check protocol: Run an ordered sequence of process checks, MCP initialize, doctor, memory_stats, and memory_search to verify end-to-end retrieval. - Wire protocol decoding: Parse SSE-framed MCP responses, double-encoded tools/call payloads, and nested query-guard warning annotations correctly. - Safe bank inspection: Read memory.db settings and vec0 shadow tables while the server runs, and spin up isolated scratch servers on port 0 for A/B settings tests. - Use Case: When a manual checklist item fails or retrieval quality looks wrong, use this Skill to confirm whether fusion, noise, or query-guard settings actually engaged via their telemetry gauges before blaming the binary. ## Quick Start Probe the running ai-raccoon server to confirm its health, project ID, and current settings state.