Remote MCP · Endpoint
webring.online MCP server
No. webring.online answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://webring.online/mcp
The last check completed an MCP handshake.
- Registry name
- online.webring/ring
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 338 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Traversable webring directory for the agentic web: agents, MCP servers, and agent-ready websites.
- Website
- https://webring.online/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 338 ms |
| 1 day ago | Handshake completed | 178 ms |
| 2 days ago | Handshake completed | 528 ms |
| 3 days ago | Handshake completed | 330 ms |
| 4 days ago | Handshake completed | 155 ms |
| 5 days ago | Handshake completed | 209 ms |
| 6 days ago | Handshake completed | 427 ms |
| 8 days ago | Handshake completed | 290 ms |
| 11 days ago | Handshake completed | 185 ms |
| 13 days ago | Handshake completed | 179 ms |
| 16 days ago | Handshake completed | 371 ms |
| 18 days ago | Handshake completed | 152 ms |
| 20 days ago | Handshake completed | 289 ms |
| 22 days ago | Handshake completed | 53 ms |
| 24 days ago | Handshake completed | 287 ms |
| 26 days ago | Handshake completed | 143 ms |
| 27 days ago | Handshake completed | 255 ms |
| 29 days ago | Handshake completed | 278 ms |
| 29 days ago | Handshake completed | 342 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 webring.online and makes no claim about it beyond what these checks measured.