Remote MCP · Endpoint
Spp MCP server
No. Spp answered an MCP handshake 2 hours ago.
UpLast checked 2 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
- 69 ms
- Tools exposed
- 48 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Real-time electricity data for SPP, the Southwest Power Pool grid operator covering 14 US states…
- Repository
- https://github.com/pipeworx-io/mcp-spp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 69 ms |
| 13 hours ago | Handshake completed | 136 ms |
| 1 day ago | Handshake completed | 96 ms |
| 2 days ago | Handshake completed | 84 ms |
| 4 days ago | Handshake completed | 515 ms |
| 5 days ago | Handshake completed | 140 ms |
| 5 days ago | Handshake completed | 106 ms |
| 7 days ago | Handshake completed | 156 ms |
| 9 days ago | Handshake completed | 189 ms |
| 12 days ago | Handshake completed | 74 ms |
| 14 days ago | Handshake completed | 67 ms |
| 16 days ago | Handshake completed | 52 ms |
| 19 days ago | Handshake completed | 56 ms |
| 21 days ago | Handshake completed | 75 ms |
| 23 days ago | Handshake completed | 65 ms |
| 25 days ago | Handshake completed | 57 ms |
| 26 days ago | Handshake completed | 50 ms |
| 28 days ago | Handshake completed | 83 ms |
| 29 days ago | Handshake completed | 207 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.
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.