Synap Memory

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as ai.maximem/synap and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 28 Jul 2026. Not supplied by the maker.

• 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 ke

• 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 co

• 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

• 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.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.