Skip to content
External endpointresponds

eia-energy-mcp-server

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

Endpoint URL
https://eia-energy.caseyjhand.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:01 AM UTC
Check
MCP initialize · 8s limit
Latency
426 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.cyanheads/eia-energy-mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
eia-energy-mcp-server
Version
0.4.0
Capability keys
logging, resources, tools, prompts
Tool names
eia_browse_routes, eia_describe_route, eia_search_routes, eia_query_route, eia_dataframe_describe, eia_dataframe_query
Instructions excerpt

Use the `eia_*` tools for U.S. Energy Information Administration (EIA) API v2 energy data. Requires an `EIA_API_KEY`. Routes use path identifiers (e.g. `electricity`, `petroleum/pri`); leading, trailing, and doubled slashes are stripped, so an EIA-doc spelling resolves the same way. Workflow: `eia_search_routes` or `eia_browse_routes` to find a leaf route → `eia_describe_route` for its facets and columns → `eia_query_route` with facet-ID filters. Facet values come only from describe, not route metadata, so describe before querying. Values arrive as strings. `eia_query_route` returns a preview and stages nothing by default; pass `stage: true` to also stage the matching rows as a DataCanvas table named by the `dataset` field, queried via SQL with `eia_dataframe_query`. Every dataset a tenant stages shares one canvas, so tables from different routes cross-join by name. The dataframe tools are listed only where a canvas is configured.

Reported Aug 17, 2026, 05:01 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 247ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 729ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 279ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 426ms