# MemorySync Documentation (remote · docs.memorysync.io)

Search and read the current MemorySync documentation while writing integration code.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-18

## Components

- remote · `docs.memorysync.io`: 68/100 (this document), [markdown](https://verifymcp.io/servers/io-memorysync-docs/docs.md), [page](https://verifymcp.io/servers/io-memorysync-docs/docs)

## Channel facts

- Endpoint: `https://docs.memorysync.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-18.

- **Endpoint Security**: 63/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 3 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 89/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 244 tokens (~48/item across 5 items; 3 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-memorysync-docs https://docs.memorysync.io/mcp
```

### Codex

```toml
[mcp_servers.io-memorysync-docs]
url = "https://docs.memorysync.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-memorysync-docs --url https://docs.memorysync.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-memorysync-docs:
    url: "https://docs.memorysync.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-memorysync-docs": {
      "type": "http",
      "url": "https://docs.memorysync.io/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-17 (score 68, −1)

- [functional regression] MCP protocol: pass → fail
- [functional] MCP protocol version: 2026-07-28 → 2025-06-18

### 2026-08-16 (score 69, +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-08-15 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-14 (score 68)

First indexed and scored.

## MCP tools (3)

### `search_docs` (~61 tokens)

Search MemorySync documentation

Search the MemorySync documentation and return matching pages with their headings and a link to the full Markdown text.

Input parameters:

- `limit` (integer): Maximum pages to return (1-20).
- `query` (string, required): What to search for, in natural language or keywords.

Output parameters:

- `count` (integer)
- `query` (string)
- `results` (array)

### `read_doc` (~63 tokens)

Read a documentation page

Read the full Markdown text of one documentation page. Prefer this over a search snippet when you need exact method names, parameters, fields or limits.

Input parameters:

- `path` (string, required): Page path such as '/quickstart' or '/api/memory/add', or its full URL.

Output parameters:

- `content` (string): The full page as Markdown.
- `error` (string): Present only when the page could not be read.
- `message` (string)
- `section` (string)
- `title` (string)
- `url` (string)

### `list_doc_sections` (~27 tokens)

List documentation sections

List the top-level documentation sections and how many pages each contains, to orient before searching.

Output parameters:

- `full_index_url` (string)
- `index_url` (string)
- `sections` (array)
- `total_pages` (integer)

## Diagnostics

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

## Score history

- 2026-08-18: 68
- 2026-08-17: 68
- 2026-08-16: 69
- 2026-08-15: 68
- 2026-08-14: 68

## Links

- Remote endpoint: https://docs.memorysync.io/mcp
- Website: https://docs.memorysync.io/mcp/overview
- Changelog RSS feed: https://verifymcp.io/servers/io-memorysync-docs/docs.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-memorysync-docs/docs.json
- HTML version of this page: https://verifymcp.io/servers/io-memorysync-docs/docs