Remote MCP · Endpoint
The New Engineer — HVAC MCP server
Yes, as of 57 minutes ago: the server returned an HTTP error.
DownLast checked 57 minutes ago
Server URL
https://thenewengineer.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.thenewengineer/hvac
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- European HVAC sizing: EN 12828 expansion vessels, EN 378 zones, Swiss refrigerant rules.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 57 minutes ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Handshake completed | 345 ms |
| 1 day ago | Handshake completed | 342 ms |
| 2 days ago | Handshake completed | 425 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 4.
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 The New Engineer — HVAC and makes no claim about it beyond what these checks measured.