Remote MCP · Endpoint

Network Evidence MCP MCP server

No. Network Evidence MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://network-evidence-mcp-preview-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
521 ms
Tools exposed
3 tools
Uptime, last 30 days
100% 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).
Recent checks of Network Evidence MCP
CheckedResultHandshake
1 hour agoHandshake completed521 ms
17 hours agoHandshake completed558 ms
1 day agoHandshake completed557 ms
3 days agoHandshake completed566 ms
5 days agoHandshake completed583 ms
7 days agoHandshake completed516 ms
10 days agoHandshake completed640 ms
12 days agoHandshake completed560 ms
14 days agoHandshake completed137 ms
16 days agoHandshake completed559 ms
18 days agoHandshake completed596 ms
20 days agoHandshake completed514 ms
22 days agoHandshake completed508 ms
23 days agoHandshake completed531 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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.