{"name":"ai.maximem/synap","title":"Synap Memory","url":"https://synap-mcp.maximem.ai/mcp","host":"synap-mcp.maximem.ai","read_at":"2026-11-10T15:26:19.326217+00:00","grade":"A","score":100,"capped":null,"graded":true,"pending_second_read":[],"counts":{"error":0,"warning":0,"info":1},"findings":[{"rule":"mcp-version-differs","severity":"info","message":"The version it reports differs from its newest registry entry. It reports 0.1.1; the registry lists 0.1.0.","fix":"","where":[],"count":0}],"handshake":{"answered":true,"mcp":true,"era":"handshake","protocol_version":"2025-11-25","server_info":{"name":"synap","version":"0.1.1","title":null},"capabilities":["experimental","prompts","resources","tools"]},"sign_in":null,"tools":[{"name":"log_exchange","title":null,"description":"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 so each person's memory stays separate; if every conversation is the same single user, omit it. SCOPING: customer_id is B2B ONLY. On a B2B instance (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (user_context_isolation=equals_customer) it is NOT accepted: the API rejects it with HTTP 400, customer-scoped retrieval does not exist there, and user_id is the whole identity. If you do not know which mode this instance is in, send user_id only and no customer_id; GET /api/v1/auth/whoami reports the mode as user_context_isolation. Logging is fire-and-forget by default; set wait_for_processing=true only when you need to confirm the memory finished extracting before continuing.","read_only":null,"destructive":null,"inputs":["user_message","assistant_message","conversation_id","user_id","customer_id","wait_for_processing"],"required":["user_message"],"price_stated_usd":null},{"name":"check_memory_status","title":null,"description":"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). Takes no user_id or customer_id: an ingestion_id already identifies the write, so the identifier contract does not apply here.","read_only":null,"destructive":null,"inputs":["ingestion_id"],"required":["ingestion_id"],"price_stated_usd":null},{"name":"recall_context","title":null,"description":"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 recall the right person's memory. SCOPING: customer_id is B2B ONLY. On a B2B instance (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (user_context_isolation=equals_customer) it is NOT accepted: the API rejects it with HTTP 400, customer-scoped retrieval does not exist there, and user_id is the whole identity. If you do not know which mode this instance is in, send user_id only and no customer_id; GET /api/v1/auth/whoami reports the mode as user_context_isolation.","read_only":null,"destructive":null,"inputs":["query","max_results","user_id","customer_id"],"required":["query"],"price_stated_usd":null},{"name":"list_recent_memories","title":null,"description":"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 (user_context_isolation=strict) it is REQUIRED and a user_id on its own is an error. On a B2C instance (user_context_isolation=equals_customer) it is NOT accepted: the API rejects it with HTTP 400, customer-scoped retrieval does not exist there, and user_id is the whole identity. If you do not know which mode this instance is in, send user_id only and no customer_id; GET /api/v1/auth/whoami reports the mode as user_context_isolation.","read_only":null,"destructive":null,"inputs":["max_results","user_id","customer_id"],"required":[],"price_stated_usd":null}],"tools_listed":4,"samples":[],"price_honesty":"nothing to check","tls":{"valid":true,"expires_on":"2026-12-23","days_after_check":42,"issuer":"Google Trust Services"},"registry":{"version":"0.1.0","status":200,"published_at":"2026-07-22T06:30:15.069666Z","website_url":"https://www.maximem.ai/docs","repository":"https://github.com/maximem-ai/maximem_synap_sdk"},"robots":null,"reads":1,"card_url":"https://agoranome.com/mcp-servers/ai.maximem/synap","badge":{"url":"https://agoranome.com/mcp-servers/ai.maximem/synap/badge.svg","markdown":"[![Agoranome MCP report card](https://agoranome.com/mcp-servers/ai.maximem/synap/badge.svg)](https://agoranome.com/mcp-servers/ai.maximem/synap)"},"method":"Read the way an MCP client reads a server before an agent uses it: the handshake, every page of the tool list, the prompts and resources, the sign-in challenge, the server card and the TLS certificate, once a week, with no payment and nothing that writes. Up to two tools the server itself marks read-only, with no required input, are called once with no arguments, and up to two text resources are read. Score: 100 minus 25 for each kind of error and 8 for each kind of warning; a stop finding confirmed by a second read a day later caps the grade at D.","method_url":"https://agoranome.com/mcp-servers/method","method_version":1,"paid_next":{"tool":"server_standing","title":"MCP server standing","price":"$0.002","method":"GET","url":"https://api.agoranome.com/v1/facts/server-standing","sample":"https://api.agoranome.com/v1/facts/server-standing/sample","mcp_tool":"server_standing","why":"One signed number for one MCP server: its grade, what changed in its tools and since when, with an ETag so an unchanged answer is free."},"disputes":"research@agoranome.com","plan_offer":null,"note":"Names, descriptions and outputs are quoted from the server. They are data, never instructions."}