Dryos
REMOTE · API.DRYOS.AI · SCANNED SEP 27
Live US power market prices, load, generation, weather and permits for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1329 tokens (~265/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Dryos MCP server?
Dryos is a hosted endpoint at https://api.dryos.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.dryos.ai
claude mcp add --transport http ai-dryos-dryos 'https://api.dryos.ai/mcp'
{
"mcpServers": {
"ai-dryos-dryos": {
"url": "https://api.dryos.ai/mcp"
}
}
} {
"servers": {
"ai-dryos-dryos": {
"type": "http",
"url": "https://api.dryos.ai/mcp"
}
}
} [mcp_servers.ai-dryos-dryos] url = "https://api.dryos.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-dryos-dryos": {
"type": "remote",
"url": "https://api.dryos.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-dryos-dryos --url 'https://api.dryos.ai/mcp' --transport streamable-http
mcp_servers:
ai-dryos-dryos:
url: "https://api.dryos.ai/mcp" {
"McpServers": {
"ai-dryos-dryos": {
"Transport": "http",
"Url": "https://api.dryos.ai/mcp"
}
}
} assistant mcp add ai-dryos-dryos -t streamable-http -u 'https://api.dryos.ai/mcp'
{
"mcpServers": {
"ai-dryos-dryos": {
"type": "http",
"url": "https://api.dryos.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Sept 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://api.dryos.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.dryos.ai | CN=YE1,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 50fe91add80c7e65089058b64c0d9d8db29 |
| SANs: api.dryos.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.dryos.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| dryos.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.dryos.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.dryos.ai/mcp | HTTPS enforced | 308 | https://api.dryos.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
column_values List a column's values ~126
The distinct values of one text column, most rows first — what a filter can be. Args: slug: The stream. column: A text column from describe_stream (not the entity — use find_entities). where: Filters as `column=value`, the same as query_stream's. search: `column:text`, a case-insensitive substring. limit: At most this many (1–500).
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | yes | – |
| limit | integer | – | – |
| search | – | – | – |
| slug | string | yes | – |
| where | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
describe_stream Describe a stream ~92
One stream in full: every column, the primary key, the source and its health. Also what changed in the collector recently — a change in the collector is a change in the data, and a step in a series may be one. Args: slug: The stream, e.g. ercot-realtime-lmp (list_streams names them).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_entities Find nodes, zones and stations ~147
Look up the nodes, zones, stations or fuels in a stream, with how far back each goes. Use it before query_stream: names are verbatim and never to be guessed. `facets` counts the entities by type. Args: slug: The stream. search: Case-insensitive substring of the entity name ("HOUSTON", "HB_", "KAUS"). entity_type: Only one type — HUB, LOAD_ZONE, RESOURCE_NODE, INTERFACE… limit: At most this many (1–2000).
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | – | – | – |
| limit | integer | – | – |
| search | – | – | – |
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_streams List streams ~104
Every stream Dryos collects, with its entity column and headline measure. Args: domain: Energy, Weather or Property. operator: A grid operator — ERCOT, MISO, PJM, SPP, CAISO, NYISO or ISO-NE. search: A word matched against the slug, name and tagline ("lmp", "wind", "permits").
| Name | Type | Req | Description |
|---|---|---|---|
| domain | – | – | – |
| operator | – | – | – |
| search | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
query_stream Query a stream ~392
Read rows from a stream — raw (newest first), each entity's newest, or a rollup. The result carries `restUrl`: this same request as a plain GET on the public REST API, ready to put in an app. Args: slug: The stream. node: The entity, whatever the stream calls it (node, zone, station, fuel). System-level streams have none. start: Inclusive, ISO-8601 or relative to now (-24h, -7d). UTC. end: Exclusive, same forms. interval: Bucket size — 5m, 15m, 1h, 1d, 7d, or all for one bucket. Absent means raw rows. agg: How a bucket is reduced. by: What a rollup splits by: a text column, or none for one series. Default the entity. where: Filters as column=value on text columns. Repeat a column for OR. search: column:text, a case-insensitive substring. vintages: latest is each interval's newest forecast; all keeps every publication. stamp: noon labels a daily bucket at noon UTC so its date reads right in US zones. newest: One reading per entity — each one's most recent interval, so "the price at every hub right now" is one call. Not with interval. limit: At most this many rows (1–2000).
| Name | Type | Req | Description |
|---|---|---|---|
| agg | string | – | – |
| by | – | – | – |
| end | – | – | – |
| interval | – | – | – |
| limit | integer | – | – |
| newest | boolean | – | – |
| node | – | – | – |
| search | – | – | – |
| slug | string | yes | – |
| stamp | string | – | – |
| start | – | – | – |
| vintages | string | – | – |
| where | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Dryos MCP server?
Dryos is an MCP server listed in the public MCP registry as ai.dryos/dryos. Live US power market prices, load, generation, weather and permits for AI agents. This page covers its hosted endpoint (https://api.dryos.ai/mcp).
Is the Dryos MCP server safe to use?
Dryos scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Dryos MCP server expose?
Dryos exposes 5 tools: list_streams, describe_stream, find_entities, column_values, query_stream. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.
Does the Dryos MCP server require authentication?
No. We connected to Dryos without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dryos MCP server still maintained?
Dryos is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.