Remote MCP · Endpoint

Ferc Eqr MCP server

No. Ferc Eqr answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/ferc-eqr/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ferc-eqr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.10 s
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
FERC Electric Quarterly Reports (EQR) — wholesale power sales: who sells to whom, under what…
Listing
From the official MCP registry (active).
Recent checks of Ferc Eqr
CheckedResultHandshake
1 hour agoHandshake completed1.10 s
9 days agoHandshake completed217 ms
10 days agoHandshake completed1.21 s
11 days agoHandshake completed965 ms
12 days agoHandshake completed169 ms
14 days agoHandshake completed98 ms
14 days agoHandshake completed714 ms
15 days agoHandshake completed174 ms
17 days agoHandshake completed130 ms
19 days agoHandshake completed684 ms
22 days agoHandshake completed2.68 s
24 days agoHandshake completed120 ms
26 days agoHandshake completed77 ms
28 days agoHandshake completed66 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 Ferc Eqr and makes no claim about it beyond what these checks measured.