Remote MCP · Endpoint

OPC UA NodeSet Gate MCP server

No. OPC UA NodeSet Gate answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://nodeset.regevidencehub.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
5 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Deterministic release-compatibility preflight for OPC UA NodeSet2 XML.
Listing
From the official MCP registry (active).
Recent checks of OPC UA NodeSet Gate
CheckedResultHandshake
4 hours agoHandshake completed159 ms
2 days agoHandshake completed115 ms
4 days agoHandshake completed128 ms
6 days agoHandshake completed125 ms
8 days agoHandshake completed118 ms
10 days agoHandshake completed124 ms
12 days agoHandshake completed157 ms
13 days agoHandshake completed136 ms
14 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed145 ms
18 days agoHandshake completed119 ms
20 days agoHandshake completed115 ms
21 days agoHandshake completed155 ms
23 days agoHandshake completed149 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 OPC UA NodeSet Gate and makes no claim about it beyond what these checks measured.