Remote MCP · Endpoint
Network Evidence MCP MCP server
No. Network Evidence MCP answered an MCP handshake 58 minutes ago.
UpLast checked 58 minutes ago
Server URL
https://network-evidence-mcp-jrkc26rjga-ew.a.run.app/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.ZzNible/network-evidence
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 589 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 92.9% from 14 checks
- Described by its publisher as
- Read-only offline network profiles, caller-supplied Discovery and historical/synthetic cases.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 58 minutes ago | Handshake completed | 589 ms |
| 13 hours ago | Handshake completed | 569 ms |
| 1 day ago | Handshake completed | 546 ms |
| 2 days ago | Handshake completed | 501 ms |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Handshake completed | 107 ms |
| 9 days ago | Handshake completed | 575 ms |
| 12 days ago | Handshake completed | 561 ms |
| 14 days ago | Handshake completed | 521 ms |
| 16 days ago | Handshake completed | 552 ms |
| 18 days ago | Handshake completed | 532 ms |
| 20 days ago | Handshake completed | 557 ms |
| 22 days ago | Handshake completed | 506 ms |
| 23 days ago | Handshake completed | 555 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 14.
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 Evidence MCP and makes no claim about it beyond what these checks measured.