Remote MCP · Endpoint

Behind the Watt MCP server

No. Behind the Watt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.behindthewatt.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ykorets/behind-the-watt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
241 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified behind-the-meter data center power, announcements, and provenance receipts.
Listing
From the official MCP registry (active).
Recent checks of Behind the Watt
CheckedResultHandshake
1 hour agoHandshake completed241 ms
9 days agoHandshake completed284 ms
10 days agoHandshake completed155 ms
11 days agoHandshake completed171 ms
12 days agoHandshake completed203 ms
14 days agoHandshake completed265 ms
14 days agoHandshake completed154 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed201 ms
19 days agoHandshake completed328 ms
21 days agoHandshake completed191 ms
24 days agoHandshake completed208 ms
26 days agoHandshake completed322 ms
28 days agoHandshake completed196 ms

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

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 Behind the Watt and makes no claim about it beyond what these checks measured.