Remote MCP · Endpoint

Openei Urdb MCP server

No. Openei Urdb answered an MCP handshake 23 hours ago.

UpLast checked 23 hours ago

Server URL

https://gateway.pipeworx.io/openei-urdb/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/openei-urdb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
OpenEI Utility Rate Database (URDB) MCP
Listing
From the official MCP registry (active).
Recent checks of Openei Urdb
CheckedResultHandshake
23 hours agoHandshake completed87 ms
3 days agoHandshake completed245 ms
5 days agoHandshake completed55 ms
6 days agoHandshake completed50 ms
8 days agoHandshake completed71 ms
9 days agoHandshake completed50 ms
10 days agoHandshake completed37 ms
13 days agoHandshake completed40 ms
15 days agoHandshake completed59 ms
16 days agoHandshake completed73 ms
18 days agoHandshake completed53 ms
19 days agoHandshake completed41 ms
20 days agoHandshake completed44 ms
21 days agoHandshake completed39 ms
21 days agoHandshake completed43 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 Openei Urdb and makes no claim about it beyond what these checks measured.