Remote MCP · Endpoint

Loop Breaker MCP server

No. Loop Breaker answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://loop.cloudforbots.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/loop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
224 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Catch AI agent loops: halt runs that repeat the same failing step or tool call.
Listing
From the official MCP registry (active).
Recent checks of Loop Breaker
CheckedResultHandshake
12 minutes agoHandshake completed224 ms
9 days agoHandshake completed184 ms
9 days agoHandshake completed227 ms
11 days agoHandshake completed312 ms
12 days agoHandshake completed223 ms
13 days agoHandshake completed201 ms
14 days agoHandshake completed196 ms
14 days agoHandshake completed244 ms
16 days agoHandshake completed211 ms
19 days agoHandshake completed198 ms
21 days agoHandshake completed187 ms
24 days agoHandshake completed139 ms
26 days agoHandshake completed134 ms
28 days agoHandshake completed142 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 Loop Breaker and makes no claim about it beyond what these checks measured.