Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Persistent memory for AI agents — log and recall conversation context over MCP.
Facts
- MCP registry
ai.maximem/synap· 0.1.0- Endpoint
https://synap-mcp.maximem.ai/mcp- Website
- www.maximem.ai/docs
- GitHub stars
- 76
- Registry entry
- updated 22 Jul 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under maximem.ai, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 4 · about 1,748 tokens of context · checked 2 hours ago
| Tool | What it does | Hint |
|---|---|---|
log_exchange | After each user message, send the exchange here so it can be remembered. You do not need to decide what is important, just forward the user message (and your reply, if you have one) and Synap will keep what matters. If… | |
check_memory_status | Check whether a logged exchange has finished processing. Pass the ingestion_id returned by log_exchange. Returns the processing status and how many memories were extracted. Useful to confirm a save completed (extraction… | |
recall_context | Before replying, call this to recall anything already known about this user from past conversations. Use the user's latest message as the query. If you serve multiple end-users, pass the same user_id you log with so you… | |
list_recent_memories | List recent things remembered about this user. Useful for debugging or to confirm that memory is working. Pass user_id to scope to one person. SCOPING: customer_id is B2B ONLY. On a B2B instance… |
What https://synap-mcp.maximem.ai/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 8 warnings · 1 note
- warnTC11check_memory_statusits one parameter, ingestion_id, has no description
- warnTC11list_recent_memories1 parameter without a description: max_results
- warnTC11log_exchange4 parameters without a description: assistant_message, conversation_id, user_message, wait_for_processing
- warnTC11recall_context2 parameters without a description: max_results, query
- warnTC16check_memory_statusno readOnlyHint or destructiveHint
- warnTC16list_recent_memoriesno readOnlyHint or destructiveHint
- warnTC16log_exchangeno readOnlyHint or destructiveHint
- warnTC16recall_contextno readOnlyHint or destructiveHint
- noteTC29serverabout 171 tokens (9% of the definitions) are titles that repeat property or function names
The checks from /check and anchor check, run each day on the list above: about 1,748 tokens of definitions. Not part of the score yet. Check your own server.