Remote MCP · Endpoint
network MCP server
No. network answered an MCP handshake 1 hour ago.
Up · key neededLast checked 1 hour ago
Server URL
https://www.doc2mcp.site/api/mcp/627464b0-c66d-44f0-a60d-76664a9bdbb1/mcp
The handshake completes, but listing its tools needs credentials.
- Registry name
- io.github.doc2mcp/network
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 443 ms
- Tools exposed
- Behind credentials
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- MCP server for network documentation, generated by doc2mcp.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 443 ms |
| 1 day ago | Handshake completed | 300 ms |
| 2 days ago | Handshake completed | 325 ms |
| 3 days ago | Handshake completed | 431 ms |
| 4 days ago | Handshake completed | 304 ms |
| 5 days ago | Handshake completed | 264 ms |
| 6 days ago | Handshake completed | 309 ms |
| 9 days ago | Handshake completed | 519 ms |
| 11 days ago | Handshake completed | 302 ms |
| 14 days ago | Handshake completed | 1.13 s |
| 16 days ago | Handshake completed | 276 ms |
| 18 days ago | Handshake completed | 333 ms |
| 20 days ago | Handshake completed | 305 ms |
| 22 days ago | Handshake completed | 300 ms |
| 24 days ago | Handshake completed | 295 ms |
| 26 days ago | Handshake completed | 310 ms |
| 27 days ago | Handshake completed | 289 ms |
| 29 days ago | Handshake completed | 257 ms |
The last 18 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 network and makes no claim about it beyond what these checks measured.