Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.cyanheads/eia-energy-mcp-server

REMOTE · EIA-ENERGY.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 21

Browse and query the EIA API v2 — electricity, petroleum, natural gas, coal, forecasts via MCP.

0 this week 80 Trust /100
Trust breakdown (7 categories)

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2212 tokens (~368/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the io.github.cyanheads/eia-energy-mcp-server server?

io.github.cyanheads/eia-energy-mcp-server is a hosted endpoint at https://eia-energy.caseyjhand.com/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 · eia-energy.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-eia-energy-mcp-server 'https://eia-energy.caseyjhand.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cyanheads-eia-energy-mcp-server": {
      "url": "https://eia-energy.caseyjhand.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cyanheads-eia-energy-mcp-server": {
      "type": "http",
      "url": "https://eia-energy.caseyjhand.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cyanheads-eia-energy-mcp-server]
url = "https://eia-energy.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-eia-energy-mcp-server": {
      "type": "remote",
      "url": "https://eia-energy.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-eia-energy-mcp-server --url 'https://eia-energy.caseyjhand.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-eia-energy-mcp-server:
    url: "https://eia-energy.caseyjhand.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cyanheads-eia-energy-mcp-server": {
      "Transport": "http",
      "Url": "https://eia-energy.caseyjhand.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cyanheads-eia-energy-mcp-server -t streamable-http -u 'https://eia-energy.caseyjhand.com/mcp'
// mcp.json
{
  "mcpServers": {
    "cyanheads-eia-energy-mcp-server": {
      "type": "http",
      "url": "https://eia-energy.caseyjhand.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 19 Sept 26 0
    • Server version: 0.4.1 → 0.4.2 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 −1
    • Stability: pass → 0.93 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.4.0 → 0.4.1 functional
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 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
Diagnostics

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 20 Sept 2026 · Probed https://eia-energy.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 4 Sept 2026 3 Dec 2026 ECDSA 256 ECDSA-SHA256 a6985204ed51ae050e7738aa6be668e9
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of eia-energy.caseyjhand.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
eia-energy.caseyjhand.com. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://eia-energy.caseyjhand.com/mcp Verified 200
http (plaintext) http://eia-energy.caseyjhand.com/mcp HTTPS enforced 301 https://eia-energy.caseyjhand.com/mcp
MCP tools · 6 exposed · ~1,985 tokens

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 →

Tool Tokens
eia_browse_routes ~172

Lists child routes under a given path in the EIA dataset taxonomy. Start with no path to get the 14 top-level categories (electricity, petroleum, natural-gas, steo, aeo, ieo, seds, etc.), then drill into subcategories. Each result includes an isLeaf flag — leaf routes are queryable endpoints; non-leaf routes have children to browse. When isLeaf is true on the browsed path itself, switch to eia_describe_route.

NameTypeReqDescription
pathstringRoute path to browse (e.g. "electricity", "petroleum/pri"). Omit for root. Leading, trailing, and doubled slashes are stripped, so an EIA-doc spelling like "/electricity/retail-sales/" resolves to th…
NameTypeReqDescription
childrenarrayChild entries under the browsed path.
errorobjectPresent when the call failed. Absent on success.
isLeafbooleanTrue when the browsed path itself is a leaf route — no children to drill into; use eia_describe_route instead.
pathstringThe path that was browsed (empty string for root).

No examples provided.

eia_dataframe_describe ~200

List canvas dataframes (df_<id>) materialized by eia_query_route calls that passed stage: true, with provenance, expiry, row count, and column schema. Nothing is staged until such a call runs, so an empty list on a fresh session means no query has staged yet, not that staging failed. Drops entries for dataframes the canvas no longer holds before responding, so the list is always current. Pass a specific name to inspect one dataframe; omit to list all active dataframes for this tenant. A name that is not staged comes back as found=false alongside the handles that are, never as an empty list. Listing is not use: only an eia_dataframe_query statement naming a dataframe extends its expiry, so a dataframe polled with this tool and never queried still lapses on schedule.

NameTypeReqDescription
namestringdf_<id> handle to describe a single dataframe. Omit to list all active dataframes.
NameTypeReqDescription
active_namesarrayEvery df_<id> handle staged for this tenant, regardless of the requested scope. On a miss these are the handles that are still usable.
dataframesarrayDataframes matching the requested scope, newest first. Empty when nothing is staged, or when a supplied name does not resolve — read found and active_names to tell those apart.
errorobjectPresent when the call failed. Absent on success.
foundbooleanTrue when the requested name is staged, false when it is not. Absent when no name was supplied — an unscoped list has nothing to resolve.
requested_namestringEcho of the name input. Absent when no name was supplied.

No examples provided.

eia_dataframe_query ~411

Run a single-statement SELECT against canvas dataframes registered by eia_query_route calls that passed stage: true — a query that staged nothing leaves no table to select from. Standard DuckDB SQL — joins, aggregates, window functions, CTEs all supported. Reference dataframes by the df_<id> handles returned by eia_query_route or listed by eia_dataframe_describe. Read-only: writes, DDL, DROP, COPY, PRAGMA, ATTACH, and external-file table functions are rejected. System catalogs (information_schema, pg_catalog, sqlite_master, duckdb_*) are denied. EIA data values are VARCHAR — use CAST(col AS DOUBLE) for arithmetic and aggregation. Optional register_as chains results as a new dataframe with a fresh expiry. Every dataframe named in the statement has its expiry extended by the query.

NameTypeReqDescription
previewintegerRows to include in the immediate response. Defaults to row_limit. Set lower when chaining via register_as and only a sample is needed inline.
register_asstringWhen set, persist the result as a new dataframe with a fresh expiry. Use to chain analyses without re-running upstream queries. The name must be unused — reusing a staged name is rejected, and the fi…
row_limitintegerHard cap on rows materialized in the response (default 1000, max 10000). Rows past the cap are dropped without being counted — the response then carries truncated: true and a totalRows equal to the c…
sqlstringyesSingle-statement SELECT against df_<id> tables. EIA data columns are VARCHAR — use CAST(col AS DOUBLE) for arithmetic. Example: SELECT period, CAST(value AS DOUBLE) AS val FROM df_XXXXX ORDER BY peri…
NameTypeReqDescription
columnsarrayColumn names in projection order.
errorobjectPresent when the call failed. Absent on success.
executedSqlstringEcho of the SQL statement that was executed — confirms the exact query that ran.
expires_atstringISO 8601 expiry for the newly registered dataframe, when applicable. Extended each time a later query references it.
noticestringGuidance when either cap bound the response — names the cap that applied and how to reach the rows it withheld.
registered_asstringSet when register_as was supplied and the new dataframe was materialized.
returnedRowsnumberRows included in this response.
rowsarrayMaterialized rows, bounded by preview / row_limit.
totalRowsnumberRows the query materialized. Exact when truncated is false — including on the register_as path, which stages and counts the whole result past row_limit. Equal to row_limit when truncated is true: a f…
truncatedbooleanTrue when row_limit cut the result: more rows matched than the cap and the remainder was dropped without being counted. False when every matching row was materialized, including on the register_as pa…

No examples provided.

eia_describe_route ~299

Returns metadata for a leaf route: available facets with their valid values, data column names and units, frequency options, and date range. Call this before eia_query_route to discover valid facet IDs, facet values, column IDs, and frequency codes. Each facet returns a capped window of its values with value_count and values_truncated alongside; pass facet and values_offset to page through the rest of one facet. A values_offset past the last value of a facet returns an empty window for it and a notice naming the count to page against. Facet values are fetched from separate EIA endpoints and merged — results are cached per-route for the process lifetime to minimize API calls.

NameTypeReqDescription
facetstringRestrict the response to one facet by ID (e.g. "stateid"). Use with values_offset to page a facet whose values were truncated. Omit to get every facet.
routestringyesLeaf route path (e.g. "electricity/retail-sales", "steo"). Discoverable via eia_browse_routes or eia_search_routes. Leading, trailing, and doubled slashes are stripped, so an EIA-doc spelling like "/…
values_offsetintegerIndex of the first facet value to return, applied to every facet in the response. Use the value named in a truncation hint to continue past the cap.
NameTypeReqDescription
data_columnsarrayData columns available for this route.
date_rangeobjectAvailable date range for this route.
default_date_formatstringPeriod format for the default frequency (e.g. "YYYY-MM").
default_frequencystringDefault frequency ID used when none is specified.
descriptionstringHuman-readable description of the dataset.
errorobjectPresent when the call failed. Absent on success.
facetsarrayFilterable dimensions. Each facet has an ID and a window of its valid values. Restricted to one entry when the facet input is set.
frequenciesarrayValid frequency options for eia_query_route.
noticestringGuidance when values_offset lands past the last value of one or more facets — names each emptied facet, its value_count, and its last valid offset. Absent when every facet returned values.
routestringThe route path described.
values_offsetnumberIndex of the first facet value returned, echoing the requested offset.

No examples provided.

eia_query_route ~608

Fetches data from a leaf route with optional facet filters, date range, frequency, and column selection. Use eia_describe_route first to discover valid facet IDs, facet values, column IDs, and frequency codes. Data values are strings in the response (EIA API returns all numeric values as strings, e.g. "9.13"); cast to DOUBLE in SQL when arithmetic is needed. Returns a preview inline and stages nothing by default — one upstream request, whatever total says. Pass stage: true to also page past the preview and stage the accumulated set as a DataCanvas table, then pass the returned dataset name to eia_dataframe_query for SQL. Every dataset a tenant stages lands in the same canvas, so tables from different routes cross-join by name with nothing to thread between calls.

NameTypeReqDescription
columnsarrayData column IDs to return (reduces payload). Defaults to all. IDs discoverable via eia_describe_route.
endstringPeriod end (same format as start).
filtersobjectFacet filters keyed by facet ID (e.g. { "stateid": "TX", "sectorid": ["RES", "COM"] }). Use the facets[].id values returned by eia_describe_route as keys here.
frequencystringAggregation frequency ID (e.g. "monthly", "annual"). Defaults to route default. Valid IDs from eia_describe_route.
lengthintegerRows in the inline preview (default 100, max 5000 per EIA limit). With stage: true, staging is not bounded by this — it pages past the preview on its own.
offsetintegerRow offset into the matching set (default 0). An offset at or beyond total returns zero rows.
routestringyesLeaf route path (e.g. "electricity/retail-sales", "steo"). Discoverable via eia_browse_routes or eia_search_routes. Leading, trailing, and doubled slashes are stripped, so an EIA-doc spelling like "/…
sortarrayResult ordering.
stagebooleanStage the matching rows as a DataCanvas table for SQL (default false). Off, the call makes one upstream request and returns the preview alone. On, the service pages past the preview up to EIA_CANVAS_…
startstringPeriod start in the route date format (e.g. "2020-01" for monthly, "2020" for annual). Format from eia_describe_route.
NameTypeReqDescription
appliedColumnsarrayEcho of the column projection as applied, when columns were provided.
appliedEndstringEcho of the end period as applied, when an end was provided.
appliedFiltersobjectFacet filters applied to the query, when provided.
appliedFrequencystringEcho of the frequency as applied, when a frequency was provided.
appliedLengthnumberPreview row count requested for this call.
appliedOffsetnumberRow offset applied to the query — the cause when a page comes back empty.
appliedSortarrayEcho of the result ordering as applied, when a sort was provided — the ordering that decided which rows a capped stage holds.
appliedStartstringEcho of the start period as applied, when a start was provided.
canvas_preview_notestringHuman-readable note when total exceeds the inline preview. On a stage: true call it names how many rows actually reached the canvas table, and where in the matching set those rows sit whenever the st…
dataarrayPreview rows. All numeric values are strings per the EIA API (e.g. "9.13"). Cast to DOUBLE in SQL for arithmetic: CAST(value AS DOUBLE). Per-column units appear as {col}-units fields inline in each r…
datasetstringdf_<id> table handle for the registered dataset — pass directly to eia_dataframe_query SQL (SELECT ... FROM df_<id>). Present only on a stage: true call against a deployment with a canvas configured;…
date_formatstringPeriod format for the returned data (e.g. "YYYY-MM").
effectiveRoutestringThe route path that was queried.
errorobjectPresent when the call failed. Absent on success.
frequencystringFrequency of the returned data.
noticestringInformational message when the response carries no rows — either zero rows matched the filters (broaden the query) or offset paged past the last row (reduce offset below total).
returnedCountnumberRows in this response. When returnedCount < totalCount, use offset or canvas for the rest.
returned_countnumberNumber of rows in this response. When returned_count < total, use offset pagination or DataCanvas for the rest.
routestringThe route path queried, in canonical spelling — any leading, trailing, or doubled slashes the input carried are stripped. Reusable verbatim in a follow-up call.
totalnumberTotal matching rows in the EIA dataset for this query (may exceed returned rows when pagination or spillover applies).
totalCountnumberTotal matching rows in the EIA dataset.
truncation_warningstringUpstream advisories forwarded verbatim from EIA's warnings[], joined with '; ' when more than one applies. These describe the inline page — EIA's "incomplete return" entry fires whenever the requeste…

No examples provided.

eia_search_routes ~295

Fuzzy text search across route names, descriptions, and category labels. Resolves natural-language queries like "electricity retail sales by state" or "natural gas imports" to matching route paths. Multi-term queries are also matched term by term, so combining a commodity, a metric, and a sector — "electricity price residential", "coal generation industrial sector" — reaches the route carrying that data even when no single entry reads like the whole phrase. STEO series names are indexed so queries like "ethanol net imports" or "crude oil production forecast" also resolve, and so are facet values, so a fuel type or sector term like "wind" or "anthracite coal" resolves to the route that exposes it, with filter_hint carrying the filter to pass on. Results include isLeaf so you know whether to browse further or query directly. Results with score > 0.72 are weak matches — try a more specific query or use eia_browse_routes to explore the taxonomy. The first call after server start waits 24-30s while the index warms, and at most 45s; every later call returns in milliseconds. Check indexComplete before reading anything into a short or empty result set.

NameTypeReqDescription
limitintegerMaximum results to return (default 10, max 30).
querystringyesFree-text search terms to match against route names and descriptions.
NameTypeReqDescription
capnumberThe limit that was applied.
effectiveQuerystringQuery as submitted to the Fuse.js index.
errorobjectPresent when the call failed. Absent on success.
indexCompletebooleanTrue when this answer was ranked against the complete corpus. False means part of it is missing (see indexGaps) — results may be short, and a better match may exist that was never scored.
indexGapsarrayPresent only when indexComplete is false: route paths whose metadata could not be fetched (call eia_browse_routes on one to re-fetch it) and index passes that did not land ("steo_series", "facet_valu…
noticestringRecovery hint when no routes matched — suggests alternative queries or using eia_browse_routes.
resultsarrayRanked matches, best first.
shownnumberNumber of results returned.
totalIndexednumberTotal entries in the search index (routes + STEO series names + facet values).
truncatedbooleanTrue when matches were capped at limit; more may exist.

No examples provided.

Common questions

What is the io.github.cyanheads/eia-energy-mcp-server server?

io.github.cyanheads/eia-energy-mcp-server is listed in the public MCP registry as io.github.cyanheads/eia-energy-mcp-server. Browse and query the EIA API v2, electricity, petroleum, natural gas, coal, forecasts via MCP. This page covers its hosted endpoint (https://eia-energy.caseyjhand.com/mcp).

Is the io.github.cyanheads/eia-energy-mcp-server server safe to use?

io.github.cyanheads/eia-energy-mcp-server scores 80 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 io.github.cyanheads/eia-energy-mcp-server server expose?

io.github.cyanheads/eia-energy-mcp-server exposes 6 tools: eia_browse_routes, eia_describe_route, eia_search_routes, eia_query_route, eia_dataframe_describe, eia_dataframe_query. Their descriptions and schemas cost roughly 1,985 tokens of context every time the server is loaded.

Does the io.github.cyanheads/eia-energy-mcp-server server require authentication?

No. We connected to io.github.cyanheads/eia-energy-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cyanheads/eia-energy-mcp-server server still maintained?

io.github.cyanheads/eia-energy-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.