Remote MCP · Endpoint

RegEvidenceHub CableCert MCP server

No. RegEvidenceHub CableCert answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://cablecert.regevidencehub.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ChanghuLiu/cablecert-qa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Independent owner-side QA for structured-cabling certification closeout evidence.
Listing
From the official MCP registry (active).
Recent checks of RegEvidenceHub CableCert
CheckedResultHandshake
4 days agoHandshake completed122 ms
4 days agoHandshake completed117 ms
5 days agoHandshake completed116 ms
7 days agoHandshake completed113 ms
8 days agoHandshake completed113 ms
9 days agoHandshake completed116 ms
10 days agoHandshake completed158 ms
10 days agoHandshake completed134 ms
12 days agoHandshake completed121 ms
15 days agoHandshake completed108 ms
17 days agoHandshake completed119 ms
20 days agoHandshake completed141 ms
22 days agoHandshake completed123 ms
24 days agoHandshake completed126 ms
26 days agoHandshake completed109 ms
28 days agoHandshake completed106 ms
30 days agoHandshake completed130 ms
32 days agoHandshake completed109 ms
33 days agoHandshake completed118 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 26.

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 RegEvidenceHub CableCert and makes no claim about it beyond what these checks measured.