# Synap Memory (remote · synap-mcp.maximem.ai)

Persistent memory for AI agents — log and recall conversation context over MCP.

- Trust score: 58/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `synap-mcp.maximem.ai`: 58/100 (this document), [markdown](https://verifymcp.io/servers/ai-maximem-synap/synap-mcp.md), [page](https://verifymcp.io/servers/ai-maximem-synap/synap-mcp)

## Channel facts

- Endpoint: `https://synap-mcp.maximem.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 411 tokens (~102/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-maximem-synap https://synap-mcp.maximem.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-maximem-synap]
url = "https://synap-mcp.maximem.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-maximem-synap": {
      "type": "remote",
      "url": "https://synap-mcp.maximem.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-maximem-synap --url https://synap-mcp.maximem.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-maximem-synap:
    url: "https://synap-mcp.maximem.ai/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 54, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (4)

### `log_exchange` (~172 tokens)

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 (or an organization id as customer_id) so each person's memory stays separate; if every conversation is the same single user, omit them. Logging is fire-and-forget by default; set wait_for_processing=true only when you need to confirm the memory finished extracting before continuing.

Input parameters:

- `assistant_message` (string)
- `conversation_id`
- `customer_id`
- `user_id`
- `user_message` (string, required)
- `wait_for_processing` (boolean)

Output parameters:

- `result` (string)

### `check_memory_status` (~58 tokens)

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

Input parameters:

- `ingestion_id` (string, required)

Output parameters:

- `result` (string)

### `recall_context` (~87 tokens)

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.

Input parameters:

- `customer_id`
- `max_results`
- `query` (string, required)
- `user_id`

Output parameters:

- `result` (string)

### `list_recent_memories` (~60 tokens)

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.

Input parameters:

- `customer_id`
- `max_results` (integer)
- `user_id`

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-maximem-synap/synap-mcp#diagnostics

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 57
- 2026-07-31: 56
- 2026-07-30: 56
- 2026-07-29: 56
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 54

## Links

- Remote endpoint: https://synap-mcp.maximem.ai/mcp
- Authorisation metadata: https://synap-mcp.maximem.ai/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/maximem-ai/maximem_synap_sdk
- Website: https://www.maximem.ai/docs
- Changelog RSS feed: https://verifymcp.io/servers/ai-maximem-synap/synap-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-maximem-synap/synap-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-maximem-synap/synap-mcp