Remote MCP · Endpoint
Lazyweb Public Discovery MCP server
No. Lazyweb Public Discovery answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://www.lazyweb.com/mcp/public
The last check completed an MCP handshake.
- Registry name
- com.lazyweb/discovery
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 567 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Keyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence.
- Website
- https://www.lazyweb.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 567 ms |
| 19 hours ago | Handshake completed | 608 ms |
| 2 days ago | Handshake completed | 321 ms |
| 3 days ago | Handshake completed | 397 ms |
| 4 days ago | Handshake completed | 405 ms |
| 5 days ago | Handshake completed | 540 ms |
| 6 days ago | Handshake completed | 383 ms |
| 7 days ago | Handshake completed | 514 ms |
| 10 days ago | Handshake completed | 488 ms |
| 13 days ago | Handshake completed | 388 ms |
| 15 days ago | Handshake completed | 349 ms |
| 17 days ago | Handshake completed | 572 ms |
| 19 days ago | Handshake completed | 540 ms |
| 21 days ago | Handshake completed | 330 ms |
| 23 days ago | Handshake completed | 617 ms |
| 25 days ago | Handshake completed | 402 ms |
| 27 days ago | Handshake completed | 520 ms |
| 28 days ago | Handshake completed | 572 ms |
| 29 days ago | Handshake completed | 366 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 Lazyweb Public Discovery and makes no claim about it beyond what these checks measured.