Remote MCP · Endpoint

MemorySync Documentation MCP server

No. MemorySync Documentation answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://docs.memorysync.io/mcp

The last check completed an MCP handshake.

Registry name
io.memorysync/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
286 ms
Tools exposed
3 tools
Uptime, last 30 days
94.7% from 19 checks
Described by its publisher as
Search and read the current MemorySync documentation while writing integration code.
Website
https://docs.memorysync.io/mcp/overview
Listing
From the official MCP registry (active).
Recent checks of MemorySync Documentation
CheckedResultHandshake
1 hour agoHandshake completed286 ms
1 day agoHandshake completed131 ms
2 days agoHandshake completed906 ms
3 days agoHandshake completed107 ms
4 days agoHandshake completed118 ms
5 days agoHandshake completed94 ms
6 days agoHandshake completed136 ms
8 days agoHandshake completed123 ms
11 days agoHandshake completed105 ms
13 days agoHandshake completed139 ms
15 days agoHandshake completed122 ms
18 days agoHandshake completed132 ms
20 days agoHandshake completed167 ms
22 days agoHandshake completed96 ms
24 days agoHandshake completed963 ms
26 days agoHandshake completed132 ms
27 days agoHandshake completed133 ms
28 days agoFailed - the server returned an HTTP error—
29 days agoHandshake completed116 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with MemorySync Documentation and makes no claim about it beyond what these checks measured.