Remote MCP · Endpoint

Miso MCP server

No. Miso answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://gateway.pipeworx.io/miso/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/miso
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Real-time electricity data for MISO, the grid operator for 15 US states from Louisiana to…
Listing
From the official MCP registry (active).
Recent checks of Miso
CheckedResultHandshake
42 minutes agoHandshake completed71 ms
9 days agoHandshake completed146 ms
10 days agoHandshake completed117 ms
11 days agoHandshake completed88 ms
12 days agoHandshake completed83 ms
14 days agoHandshake completed122 ms
14 days agoHandshake completed110 ms
15 days agoHandshake completed102 ms
17 days agoHandshake completed154 ms
19 days agoHandshake completed211 ms
21 days agoHandshake completed62 ms
24 days agoHandshake completed128 ms
26 days agoHandshake completed54 ms
28 days agoHandshake completed1.54 s

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