Remote MCP · Endpoint

Spp MCP server

No. Spp answered an MCP handshake 16 hours ago.

UpLast checked 16 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/spp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
75 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Real-time electricity data for SPP, the Southwest Power Pool grid operator covering 14 US states…
Listing
From the official MCP registry (active).
Recent checks of Spp
CheckedResultHandshake
16 hours agoHandshake completed75 ms
2 days agoHandshake completed65 ms
4 days agoHandshake completed57 ms
6 days agoHandshake completed50 ms
8 days agoHandshake completed83 ms
9 days agoHandshake completed207 ms
10 days agoHandshake completed55 ms
13 days agoHandshake completed42 ms
14 days agoHandshake completed49 ms
16 days agoHandshake completed38 ms
17 days agoHandshake completed70 ms
19 days agoHandshake completed36 ms
20 days agoHandshake completed41 ms
21 days agoHandshake completed46 ms
21 days agoHandshake completed42 ms

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

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