Remote MCP · Endpoint

PJM vs MISO Energy Arbitrage Oracle MCP server

Yes, as of 58 minutes ago: the connection was refused or dropped.

DownLast checked 58 minutes ago

Server URL

https://energy-arbitrage.io/mcp

The last check failed: the connection was refused or dropped.

Registry name
io.github.dornansgar390-hue/energy-oracle
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
PJM/MISO energy arbitrage. Intel TDX attested, on-chain every 60 min. MCP tools for AI agents.
Repository
https://github.com/dornansgar390-hue/energy-oracle-group
Listing
From the official MCP registry (active).
Recent checks of PJM vs MISO Energy Arbitrage Oracle
CheckedResultHandshake
58 minutes agoFailed - the connection was refused or dropped—
1 day agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with PJM vs MISO Energy Arbitrage Oracle and makes no claim about it beyond what these checks measured.