Remote MCP · Endpoint

Mem0 Cloud MCP server

Yes, as of 7 hours ago: the hostname does not resolve.

DownLast checked 7 hours ago

Server URL

https://mem0-cloud.saastemly.com/mcp

The last check failed: the hostname does not resolve.

Registry name
com.saastemly/mem0-cloud
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
69.2% from 13 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).
Recent checks of Mem0 Cloud
CheckedResultHandshake
7 hours agoFailed - the hostname does not resolve—
2 days agoFailed - the hostname does not resolve—
5 days agoFailed - the hostname does not resolve—
7 days agoFailed - the hostname does not resolve—
9 days agoHandshake completed126 ms
11 days agoHandshake completed354 ms
13 days agoHandshake completed77 ms
15 days agoHandshake completed71 ms
17 days agoHandshake completed48 ms
19 days agoHandshake completed91 ms
20 days agoHandshake completed296 ms
21 days agoHandshake completed47 ms
23 days agoHandshake completed67 ms

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

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.