Remote MCP · Endpoint
Loops: causal loop diagrams MCP server
No. Loops: causal loop diagrams answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://loops.thijsmorlion.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.morliont/loops
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 710 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Draw causal loop diagrams in the chat and edit them on a shared link.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 710 ms |
| 4 days ago | Handshake completed | 161 ms |
| 14 days ago | Handshake completed | 155 ms |
| 15 days ago | Handshake completed | 1.92 s |
| 15 days ago | Handshake completed | 755 ms |
| 17 days ago | Handshake completed | 180 ms |
| 18 days ago | Handshake completed | 818 ms |
| 19 days ago | Handshake completed | 165 ms |
| 20 days ago | Handshake completed | 100 ms |
| 21 days ago | Handshake completed | 918 ms |
| 23 days ago | Handshake completed | 1.47 s |
| 26 days ago | Handshake completed | 255 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 Loops: causal loop diagrams and makes no claim about it beyond what these checks measured.