Remote MCP · Endpoint

HMI Import Preflight MCP server

No. HMI Import Preflight answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://factorytalk.regevidencehub.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ChanghuLiu/factorytalk-import-preflight
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
284 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Independent static checks for supported tag and alarm CSV import formats; no HMI or PLC access.
Listing
From the official MCP registry (active).
Recent checks of HMI Import Preflight
CheckedResultHandshake
20 minutes agoHandshake completed284 ms
8 days agoHandshake completed120 ms
9 days agoHandshake completed123 ms
11 days agoHandshake completed117 ms
12 days agoHandshake completed115 ms
13 days agoHandshake completed109 ms
14 days agoHandshake completed121 ms
14 days agoHandshake completed215 ms
16 days agoHandshake completed120 ms
19 days agoHandshake completed125 ms
21 days agoHandshake completed118 ms
24 days agoHandshake completed106 ms
26 days agoHandshake completed131 ms
28 days agoHandshake completed119 ms

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

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