Remote MCP · Endpoint

Run Memory MCP server

No. Run Memory answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://memory.cloudforbots.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/memory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
224 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Checkpoint and resume for AI agent runs, so crashed runs pick up where they left off.
Listing
From the official MCP registry (active).
Recent checks of Run Memory
CheckedResultHandshake
12 minutes agoHandshake completed224 ms
9 days agoHandshake completed187 ms
9 days agoHandshake completed172 ms
11 days agoHandshake completed178 ms
12 days agoHandshake completed286 ms
13 days agoHandshake completed180 ms
14 days agoHandshake completed281 ms
14 days agoHandshake completed502 ms
16 days agoHandshake completed195 ms
19 days agoHandshake completed174 ms
21 days agoHandshake completed170 ms
24 days agoHandshake completed134 ms
26 days agoHandshake completed137 ms
28 days agoHandshake completed124 ms

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

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 Run Memory and makes no claim about it beyond what these checks measured.