---
name: status
description: Check memtomem configuration, storage, index counts, dense coverage, and warnings. Use when search is empty, degraded, or needs diagnosis.
allowed-tools: mcp__plugin_memtomem_memtomem__mem_status, mcp__memtomem__mem_status
---

# Check memory status
Call `mem_status` once. Report the storage backend and database path, embedding state, source and chunk counts, dense-vector coverage, and warnings that the tool actually returns.

Treat `provider=none` and BM25-only coverage as a supported default, not a failed setup. Do not claim namespace totals or other fields absent from the response.

## Registration check (Claude Code)

If both `mcp__memtomem__mem_*` and `mcp__plugin_memtomem_memtomem__mem_*`
tools are visible, warn about possible duplicate registrations. Other aliases
exposing the same memtomem tool family also warrant a check. Tool visibility
alone does not prove two live processes or a shared database; a single visible
namespace does not prove that no other registration exists.

Recommend `/mcp` first. The `--claude-mcp` diagnostic ships in the released
CLI, but installing the plugin does not put `mm` on the user's PATH — it
registers an MCP server, not the CLI. So offer the pinned form, which works
either way:

```bash
uvx --from "memtomem[all]==0.7.0" mm doctor --claude-mcp
```

This diagnostic runs in its own environment. It does not install dependencies
into, or repair, the plugin server environment.
Before installation, doctor compares manual registrations with the launch this
release's plugin bundles (`memtomem[onnx]==0.7.0`). After installation, it reads
the actual plugin manifest. Use `/mcp` to verify the session, and repeat the
diagnostic after installation.

If the user says they already have the CLI installed, `mm doctor --claude-mcp`
is the same check. Run it from the project being inspected. Neither is required
— `/mcp` and the scope-specific guidance below cover the same ground.

Use the confirmed registration name and scope for any removal advice:
`claude mcp remove memtomem -s user` is only for that user-scope name. To keep
the manual setup instead, uninstall `/plugin uninstall memtomem@memtomem`.
Never remove either registration yourself. Do not claim to have run the
diagnostic unless it was actually executed. With no visible duplication,
report the memory status normally without an extra warning.