Remote MCP · Endpoint

Synap Memory MCP server

No. Synap Memory answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://synap-mcp.maximem.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.maximem/synap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Persistent memory for AI agents — log and recall conversation context over MCP.
Listing
From the official MCP registry (active).
Recent checks of Synap Memory
CheckedResultHandshake
8 hours agoHandshake completed263 ms
2 days agoHandshake completed103 ms
4 days agoHandshake completed87 ms
5 days agoHandshake completed89 ms
7 days agoHandshake completed128 ms
8 days agoHandshake completed168 ms
9 days agoHandshake completed74 ms
12 days agoHandshake completed114 ms
13 days agoHandshake completed86 ms
15 days agoHandshake completed117 ms
16 days agoHandshake completed86 ms
17 days agoHandshake completed85 ms
18 days agoHandshake completed91 ms
19 days agoHandshake completed98 ms
20 days agoHandshake completed105 ms
21 days agoHandshake completed84 ms
23 days agoHandshake completed92 ms

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

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.

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