crystal_stats accepts optional channel, but statistics remain account-wide.
When to use
Use statistics to check account identity and active/archive counts. Use health to check connectivity and recall to find content. Counts are not a list of memories. GET or POST/api/mcp/stats returns total, archived, byStore, apiKeyLabel, account (user ID, email, and name), and flat userId/email aliases. It does not return a .usage quota object, strength distribution, strongest memories, or recent captures.
total counts active memories and can include KB chunks. It is not a cumulative creation count and is not the allowance counter. Allowance usage counts active non-KB memories only.
Stdio’s API-key JSON comes from this endpoint, but its text formatter still expects older fields. Prefer the JSON counts if its text summary disagrees.
Use health for liveness. Stats do not depend on embedding availability. What do I know retrieves bounded topic matches; it is not an enumeration API.
Parameters
Examples
Examples use placeholder IDs. Replace them with IDs returned by your account. MCP examples show the JSON tool arguments and the JSON inside the tool result, not the outer MCP envelope.Inspect account counts
Request:Interpret store counts
Use store counts to understand how your active records are distributed. A large procedural count may reflect many saved workflows or KB content; it does not prove retrieval quality.archived is separate from the active total. Compare allowance usage in the dashboard rather than subtracting totals by hand.