MCP Uptime
← MCP Reliability Index  /  AI & LLM
S

Synap Memory

ai.maximem/synap
Persistent memory for AI agents — log and recall conversation context over MCP.
healthy
status
4
tools exposed
3075ms
connect latency
3a6e3cf22ef2
schema fingerprint

Tools (4)

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 your app serves more than one end-user, pass that person's stable id as user_id
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 is asynchronous).
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 (or customer_id) you log with so you recall the right person's memory.
list_recent_memories
List recent things remembered about this user. Useful for debugging or to confirm that memory is working. Pass user_id/customer_id to scope to one person.

Endpoint

https://synap-mcp.maximem.ai/mcp
Category: AI & LLM · Last checked: 2026-08-15T08:48:43Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access
How we measure →
What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.