Remote MCP · Endpoint
WRDO MCP server
No. WRDO answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.wrdo.co.za/mcp
The last check completed an MCP handshake.
- Registry name
- za.co.wrdo/wrdo
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.95 s
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Local businesses, menus and price lists in Cape Town and the Western Cape; start a request in WRDO.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.95 s |
| 9 days ago | Handshake completed | 410 ms |
| 10 days ago | Handshake completed | 422 ms |
| 11 days ago | Handshake completed | 394 ms |
| 12 days ago | Handshake completed | 379 ms |
| 14 days ago | Handshake completed | 391 ms |
| 14 days ago | Handshake completed | 384 ms |
| 15 days ago | Handshake completed | 384 ms |
| 17 days ago | Handshake completed | 445 ms |
| 19 days ago | Handshake completed | 396 ms |
| 21 days ago | Handshake completed | 411 ms |
| 24 days ago | Handshake completed | 489 ms |
| 26 days ago | Handshake completed | 390 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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 WRDO and makes no claim about it beyond what these checks measured.