MemorySync Documentation
REMOTE · DOCS.MEMORYSYNC.IO
Search and read the current MemorySync documentation while writing integration code.
Available components
Last scanned (18 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Code Search and Documentation
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 244 tokens (~48/item across 5 items; 3 tools + 2 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 +6
- 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
- 13 Sept 26 82
- Stability: 0.97 → pass security
- 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
- 17 Aug 26 0
- MCP protocol: pass → fail ▼ functional
- MCP protocol version: 2026-07-28 → 2025-06-18 functional
- 15 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 0
First indexed and scored.
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 16 Oct 2026 · Probed https://docs.memorysync.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docs.memorysync.io | CN=YR1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | RSA 2048 | SHA256-RSA | 5f21a4e497af92c1f1a13d1fff1ddc5d74b |
| SANs: docs.memorysync.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of docs.memorysync.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| memorysync.io. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.memorysync.io/mcp | Verified | 200 | |
| http (plaintext) | http://docs.memorysync.io/mcp | HTTPS enforced | 308 | https://docs.memorysync.io/mcp |
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 →
list_doc_sections List documentation sections ~27
List the top-level documentation sections and how many pages each contains, to orient before searching.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| full_index_url | string | – | – |
| index_url | string | – | – |
| sections | array | yes | – |
| total_pages | integer | yes | – |
No examples provided.
read_doc Read a documentation page ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Page path such as '/quickstart' or '/api/memory/add', or its full URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No examples provided.
search_docs Search MemorySync documentation ~61
Search the MemorySync documentation and return matching pages with their headings and a link to the full Markdown text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum pages to return (1-20). |
| query | string | yes | What to search for, in natural language or keywords. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the MemorySync Documentation MCP server?
MemorySync Documentation is a hosted endpoint at https://docs.memorysync.io/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 · docs.memorysync.io
claude mcp add --transport http io-memorysync-docs 'https://docs.memorysync.io/mcp'
What is the MemorySync Documentation MCP server?
MemorySync Documentation is an MCP server listed in the public MCP registry as io.memorysync/docs. Search and read the current MemorySync documentation while writing integration code. This page covers its hosted endpoint (https://docs.memorysync.io/mcp).
Is the MemorySync Documentation MCP server safe to use?
MemorySync Documentation scores 88 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 MemorySync Documentation MCP server expose?
MemorySync Documentation exposes 3 tools: search_docs, read_doc, list_doc_sections. Their descriptions and schemas cost roughly 151 tokens of context every time the server is loaded.
Does the MemorySync Documentation MCP server require authentication?
No. We connected to MemorySync Documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MemorySync Documentation MCP server still maintained?
MemorySync Documentation is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.