Remote MCP · Endpoint

Ofgem MCP server

No. Ofgem answered an MCP handshake 15 hours ago.

UpLast checked 15 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/ofgem
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Ofgem energy data: the UK energy regulator's published statistics on the domestic price cap and…
Listing
From the official MCP registry (active).
Recent checks of Ofgem
CheckedResultHandshake
15 hours agoHandshake completed74 ms
2 days agoHandshake completed61 ms
4 days agoHandshake completed55 ms
6 days agoHandshake completed59 ms
8 days agoHandshake completed86 ms
9 days agoHandshake completed237 ms
10 days agoHandshake completed49 ms
13 days agoHandshake completed44 ms
14 days agoHandshake completed57 ms
16 days agoHandshake completed74 ms
17 days agoHandshake completed45 ms
19 days agoHandshake completed1.06 s
20 days agoHandshake completed41 ms
21 days agoHandshake completed41 ms
21 days agoHandshake completed55 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 Ofgem and makes no claim about it beyond what these checks measured.