Remote MCP · Endpoint

Iso Ne MCP server

No. Iso Ne answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/iso-ne/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/iso-ne
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
115 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Real-time power grid data for ISO New England, the electricity market and grid operator for…
Listing
From the official MCP registry (active).
Recent checks of Iso Ne
CheckedResultHandshake
1 hour agoHandshake completed115 ms
2 days agoHandshake completed536 ms
4 days agoHandshake completed72 ms
6 days agoHandshake completed78 ms
7 days agoHandshake completed112 ms
9 days agoHandshake completed162 ms
10 days agoHandshake completed224 ms
11 days agoHandshake completed45 ms
14 days agoHandshake completed40 ms
16 days agoHandshake completed65 ms
17 days agoHandshake completed490 ms
19 days agoHandshake completed181 ms
20 days agoHandshake completed74 ms
21 days agoHandshake completed42 ms
22 days agoHandshake completed46 ms
22 days agoHandshake completed41 ms

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

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