Remote MCP · Endpoint
RoundWatch MCP server
No. RoundWatch answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://roundwatch-api.onrender.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Vladyslav-webDev/roundwatch
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 383 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Durable Algorand USDC payment monitoring for autonomous workflows.
- Website
- https://roundwatch.observer/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 383 ms |
| 2 days ago | Handshake completed | 300 ms |
| 4 days ago | Handshake completed | 340 ms |
| 5 days ago | Handshake completed | 196 ms |
| 7 days ago | Handshake completed | 150 ms |
| 8 days ago | Handshake completed | 409 ms |
| 9 days ago | Handshake completed | 303 ms |
| 12 days ago | Handshake completed | 130 ms |
| 13 days ago | Handshake completed | 188 ms |
| 15 days ago | Handshake completed | 157 ms |
| 16 days ago | Handshake completed | 309 ms |
| 18 days ago | Handshake completed | 159 ms |
| 19 days ago | Handshake completed | 147 ms |
| 20 days ago | Handshake completed | 134 ms |
| 20 days ago | Handshake completed | 137 ms |
| 21 days ago | Handshake completed | 310 ms |
| 22 days ago | Handshake completed | 150 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 RoundWatch and makes no claim about it beyond what these checks measured.