A memory exploration and retrieval system with MCP support for storing, recalling, and managing observations and memories
memxplore provides 11 tools with complete input schemas and descriptions. Naming follows verb_noun convention (remember, recall, archive, forget, purge, export, etc.). Descriptions are present and substantive (100-200 chars typical). However, output schemas are not documented, LLMs cannot predict response structure for chaining. Parameter descriptions are good but lack explicit constraints (enums, ranges, patterns). Error handling is minimal, no recovery guidance or actionable error messages visible. Security is strong (token-based auth, scope enforcement), but composition could be tighter: remember and agent_event overlap in function.
Ingest agent events as observations with idempotent processing and optional formation
Archive a memory to mark it as inactive while preserving its data
Create a scoped API token for authentication with specific memory access permissions
Export all memories for a subject in a structured format with schema versioning
Mark a memory for forgetting to remove it from active recall while maintaining audit trail
Retrieve the status and details of a formation or lifecycle job
Health check endpoint to verify server is running
Output schemas not documented. LLMs cannot predict response structure (fields, types, nested objects) for downstream tool chaining. E.g., does recall() return memory_id, content, metadata? What is the structure of the Job object?
Parameter constraints not explicit. 'mode' in recall accepts 'lexical' or 'semantic' but no enum declared. 'visibility' accepts 'private' or 'shared' but not formalized. 'function' accepts 'factual' or 'experiential' but not constrained. LLMs will hallucinate invalid values.
No error recovery guidance. Error responses visible in code (e.g., 'remember_failed', 'invalid_wait') lack actionable next steps. LLMs receive error codes but no hint on whether to retry, ask user, or call a different tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Permanently delete a memory and all associated data (irreversible operation)
Query and retrieve memories based on owner, subject, context, and search query with configurable retrieval mode
Store an observation with optional formation strategy (generator-free or assisted) to create or update memories
Get server version and protocol information
Overlapping tool responsibilities. memxplore_remember and memxplore_agent_event both ingest observations with optional formation. Distinction unclear, when should agent use which? Violates single-responsibility principle.
Numeric parameter ranges not documented. waitMilliseconds accepts 0 - 30000, tokenBudget and candidateLimit have no stated bounds. LLMs may pass absurd values (negative, millions) causing silent failures or timeouts.