Remote MCP · Endpoint
Mem0 Cloud MCP server
No. Mem0 Cloud answered an MCP handshake 59 minutes ago.
UpLast checked 59 minutes ago
Server URL
https://mem0-cloud.saastemly.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.saastemly/mem0-cloud
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 296 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- A hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):...
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 59 minutes ago | Handshake completed | 296 ms |
| 1 day ago | Handshake completed | 47 ms |
| 3 days ago | Handshake completed | 67 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 Mem0 Cloud and makes no claim about it beyond what these checks measured.