Remote MCP · Endpoint

THE RETREAT MCP server

No. THE RETREAT answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://agentsretreat.com/mcp

The last check completed an MCP handshake.

Registry name
com.agentsretreat/the-retreat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
214 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Rules-based context reduction, planning checks, research prompts and fixed experiences for agents.
Listing
From the official MCP registry (active).
Recent checks of THE RETREAT
CheckedResultHandshake
9 hours agoHandshake completed214 ms
4 days agoHandshake completed244 ms
14 days agoHandshake completed163 ms
15 days agoHandshake completed295 ms
15 days agoHandshake completed175 ms
17 days agoHandshake completed125 ms
18 days agoHandshake completed258 ms
19 days agoHandshake completed181 ms
20 days agoHandshake completed172 ms
21 days agoHandshake completed234 ms
23 days agoHandshake completed229 ms
26 days agoHandshake completed153 ms
28 days agoHandshake completed116 ms

The last 13 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 THE RETREAT and makes no claim about it beyond what these checks measured.