Synap Memory
REMOTE · SYNAP-MCP.MAXIMEM.AI · SCANNED SEP 28
Persistent memory for AI agents — log and recall conversation context over MCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 400, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1326 tokens (~331/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Synap Memory MCP server?
Synap Memory is a hosted endpoint at https://synap-mcp.maximem.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · synap-mcp.maximem.ai
claude mcp add --transport http ai-maximem-synap 'https://synap-mcp.maximem.ai/mcp'
{
"mcpServers": {
"ai-maximem-synap": {
"url": "https://synap-mcp.maximem.ai/mcp"
}
}
} {
"servers": {
"ai-maximem-synap": {
"type": "http",
"url": "https://synap-mcp.maximem.ai/mcp"
}
}
} [mcp_servers.ai-maximem-synap] url = "https://synap-mcp.maximem.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-maximem-synap": {
"type": "remote",
"url": "https://synap-mcp.maximem.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-maximem-synap --url 'https://synap-mcp.maximem.ai/mcp' --transport streamable-http
mcp_servers:
ai-maximem-synap:
url: "https://synap-mcp.maximem.ai/mcp" {
"McpServers": {
"ai-maximem-synap": {
"Transport": "http",
"Url": "https://synap-mcp.maximem.ai/mcp"
}
}
} assistant mcp add ai-maximem-synap -t streamable-http -u 'https://synap-mcp.maximem.ai/mcp'
{
"mcpServers": {
"ai-maximem-synap": {
"type": "http",
"url": "https://synap-mcp.maximem.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_memory_status” rewrote its description, which is the text the model reads security
- Tool “list_recent_memories” rewrote its description, which is the text the model reads security
- Tool “log_exchange” rewrote its description, which is the text the model reads security
- Tool “recall_context” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 43% ▲ functional
- “list_recent_memories” reworded the description of “customer_id” cosmetic
- “list_recent_memories” reworded the description of “user_id” cosmetic
- “log_exchange” reworded the description of “customer_id” cosmetic
- “log_exchange” reworded the description of “user_id” cosmetic
- “recall_context” reworded the description of “customer_id” cosmetic
- “recall_context” reworded the description of “user_id” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://synap-mcp.maximem.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=maximem.ai | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f3bf0db6c157a5a9132d6645fe1401e3 |
| SANs: maximem.ai, *.maximem.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of synap-mcp.maximem.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| maximem.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://synap-mcp.maximem.ai/mcp | Verified | 200 | |
| http (plaintext) | http://synap-mcp.maximem.ai/mcp | Inconclusive | 400 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_memory_status ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingestion_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_recent_memories ~328
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | – | – | B2B ONLY. Required on a B2B instance (user_context_isolation=strict), where a user_id on its own is an error. NOT accepted on a B2C instance (user_context_isolation=equals_customer): the API rejects… |
| max_results | integer | – | – |
| user_id | – | – | Stable id of the end-user this call belongs to. On a B2C instance this is the ONLY identifier you send and it is the whole identity. On a B2B instance send it together with customer_id. Omit both if… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
log_exchange ~433
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assistant_message | string | – | – |
| conversation_id | – | – | – |
| customer_id | – | – | B2B ONLY. Required on a B2B instance (user_context_isolation=strict), where a user_id on its own is an error. NOT accepted on a B2C instance (user_context_isolation=equals_customer): the API rejects… |
| user_id | – | – | Stable id of the end-user this call belongs to. On a B2C instance this is the ONLY identifier you send and it is the whole identity. On a B2B instance send it together with customer_id. Omit both if… |
| user_message | string | yes | – |
| wait_for_processing | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
recall_context ~352
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | – | – | B2B ONLY. Required on a B2B instance (user_context_isolation=strict), where a user_id on its own is an error. NOT accepted on a B2C instance (user_context_isolation=equals_customer): the API rejects… |
| max_results | – | – | – |
| query | string | yes | – |
| user_id | – | – | Stable id of the end-user this call belongs to. On a B2C instance this is the ONLY identifier you send and it is the whole identity. On a B2B instance send it together with customer_id. Omit both if… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Synap Memory MCP server?
Synap Memory is an MCP server listed in the public MCP registry as ai.maximem/synap. Persistent memory for AI agents, log and recall conversation context over MCP. This page covers its hosted endpoint (https://synap-mcp.maximem.ai/mcp).
Is the Synap Memory MCP server safe to use?
Synap Memory scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Synap Memory MCP server expose?
Synap Memory exposes 4 tools: log_exchange, check_memory_status, recall_context, list_recent_memories. Their descriptions and schemas cost roughly 1,196 tokens of context every time the server is loaded.
Does the Synap Memory MCP server require authentication?
No. We connected to Synap Memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Synap Memory MCP server still maintained?
Synap Memory is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.