Remote MCP · Endpoint

Dryos MCP server

No. Dryos answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.dryos.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.dryos/dryos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
29 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Live US power market prices, load, generation, weather and permits for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Dryos
CheckedResultHandshake
2 hours agoHandshake completed29 ms
1 day agoHandshake completed154 ms
3 days agoHandshake completed31 ms
3 days agoHandshake completed26 ms
4 days agoHandshake completed35 ms
5 days agoHandshake completed24 ms
7 days agoHandshake completed28 ms
10 days agoHandshake completed25 ms
12 days agoHandshake completed23 ms
14 days agoHandshake completed70 ms
17 days agoHandshake completed65 ms
19 days agoHandshake completed303 ms
21 days agoHandshake completed24 ms
23 days agoHandshake completed28 ms
25 days agoHandshake completed26 ms
26 days agoHandshake completed25 ms
28 days agoHandshake completed22 ms
29 days agoHandshake completed24 ms

The last 18 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 Dryos and makes no claim about it beyond what these checks measured.