Remote MCP · Endpoint

Iso Ne MCP server

No. Iso Ne answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes 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
53 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 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
42 minutes agoHandshake completed53 ms
9 days agoHandshake completed126 ms
10 days agoHandshake completed119 ms
11 days agoHandshake completed81 ms
12 days agoHandshake completed130 ms
14 days agoHandshake completed94 ms
14 days agoHandshake completed463 ms
15 days agoHandshake completed103 ms
17 days agoHandshake completed148 ms
19 days agoHandshake completed144 ms
21 days agoHandshake completed53 ms
24 days agoHandshake completed131 ms
26 days agoHandshake completed71 ms
28 days agoHandshake completed115 ms

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

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.