Skip to content

eia-energy-mcp-server

io.github.cyanheads/eia-energy-mcp-servercyanheadsstreamable-httpv0.6.0Scanned

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

6 tools: 1 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 1 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the eia-energy-mcp-server can do

The eia-energy-mcp-server is published by the GitHub account cyanheads. It has 6 tools. It can create or change data (1 tool: eia_dataframe_query), but cannot delete data. 5 tools only read.

1 tool reads private data (eia_dataframe_query); 1 tool brings in text other people can write (eia_browse_routes).

The fixed checks matched 2 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.6.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 1Claude Code: ask
  • eia_dataframe_queryRun 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.Reads private data1 finding

    Why it is in this group

    • The name "eia_dataframe_query" says "query": a word for reading.
    • The description's first verb is "run": a word for a change.
    • The input takes a statement or command to run (input.sql), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "table": it reads databases.
    • private-dataThe name says "query" and the input takes a statement (input.sql): it reads databases.

    Findings

    • Warn

      The server marks "eia_dataframe_query" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "eia_dataframe_query" says "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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, file reads (read_* functions or a quoted file path), engine-setting functions (current_setting), and SQL built from a string (query_table) are rejected. System catalogs are denied: information_schema, pg_catalog, and the DuckDB internal metadata views (duckdb_tables, duckdb_columns, and the other duckdb_ views; sqlite_master and the other sqlite_ views; pragma_database_list; pg_class, pg_tables, and the other pg_ views) are refused as whole words anywhere in the statement outside string literals and comments, column aliases and CTE names included, as is any duckdb_<name>() call. A register_as name spelled like one of them is refused, since no statement could select from a table so named. 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. Inline rows stop at preview; a result cut short says how to reach the rest, including paging a register_as table with LIMIT/OFFSET and no ORDER BY, which keeps the order the preview showed.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • eia_browse_routesLists child routes under a given path in the EIA dataset taxonomy.Reads text others writeNo findings

    Why it is in this group

    • The name "eia_browse_routes" says "browse": a word for reading.

    What it can reach

    • untrusted-inputThe name "eia_browse_routes" says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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. The first call after server start waits up to 20s for the route tree to warm, then answers from EIA directly.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • eia_dataframe_describeList canvas dataframes (df_<id>) materialized by eia_query_route calls that passed stage: true, with provenance, expiry, row count, and column schema.No findings

    Why it is in this group

    • The name "eia_dataframe_describe" says "describe": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • eia_describe_routeReturns metadata for a leaf route: available facets with their valid values, data column names and units, frequency options, and date range.No findings

    Why it is in this group

    • The name "eia_describe_route" says "describe": a word for reading.
    Description, as the server wrote it
    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. To find a value by name in a large facet (plant, entity, and mine IDs run to thousands), pass values_query: each facet keeps only the values whose id, name, or alias contains it — on a balancing-authority facet, also a value whose ISO/RTO acronym does, so "ERCOT" finds ERCO — values_matched counts them, and values_offset pages the matches. 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, merged, and cached per route for 24 hours, after which the next call fetches the route again; a facet whose values EIA did not return is left out of facets, named in unavailable_facets, and fetched again by the next call. When a refresh fails, the cached values are served instead, with a notice naming when they were fetched.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • eia_query_routeFetches data from a leaf route with optional facet filters, date range, frequency, and column selection.No findings

    Why it is in this group

    • The name "eia_query_route" says "query": a word for reading.
    Description, as the server wrote it
    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_describe for its column names and 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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • eia_search_routesFuzzy text search across route names, descriptions, category labels, and the names of the data columns a route publishes.1 finding

    Why it is in this group

    • The name "eia_search_routes" says "search": a word for reading.

    Findings

    • Info

      The description is 2,279 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ex. Check indexComplete before reading anything into a short or empty result set."

      What this check looks for
    Description, as the server wrote it
    Fuzzy text search across route names, descriptions, category labels, and the names of the data columns a route publishes. Resolves natural-language queries like "electricity retail sales by state" or "natural gas imports" to matching route paths, and a measure named only by its column — "nameplate capacity", "gross generation" — to the route that publishes it. 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. A query spelling the end of a route path in words — "retail sales" for electricity/retail-sales — ranks that route first. STEO, SEDS, and Monthly Energy Review (total-energy) series names are indexed so queries like "crude oil production forecast", "motor gasoline total consumption", or "primary energy consumption total" also resolve — a series also by its ID, such as "PATCPUSX", "MGTCB", or "TETCBUS" — 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. That includes the series and product names of the daily and weekly petroleum and natural-gas routes and the RTO balancing authorities, so benchmarks like "Henry Hub", "WTI crude spot price", "Cushing", or "Electric Reliability Council of Texas" resolve before any describe; a balancing authority also answers to its EIA code or its ISO/RTO acronym ("ERCO", "ERCOT", "CAISO", "SPP"). A legacy APIv1 series ID as the EIA website and Excel add-in write them — "PET.RWTC.W", "ELEC.PRICE.TX-RES.M" — is resolved through the EIA series lookup into one result with its route, filter_hint, frequency, and columns, ready for eia_query_route, without waiting on the index. 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 20-40s while the index warms, and at most 45s; later calls answer from the built index. Check indexComplete before reading anything into a short or empty result set.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://eia-energy.caseyjhand.com/mcp: tools/list returned 6 tools to an anonymous client, including eia_dataframe_query (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "eia_dataframe_query" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "eia_dataframe_query" says "query": a word for reading.

    What this check looks for
  • The description is 2,279 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ex. Check indexComplete before reading anything into a short or empty result set."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff
  2. Tools3 changed.~3 changedView diff
  3. Tools4 changed.~4 changedView diff
  4. Tools3 changed.~3 changedView diff
  5. Tools5 changed.~5 changedView diff

Install

Pinned to version 0.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http eia-energy https://eia-energy.caseyjhand.com/mcp
claude mcp add --transport http eia-energy https://eia-energy.caseyjhand.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__eia-energy__eia_browse_routes",
      "mcp__eia-energy__eia_describe_route",
      "mcp__eia-energy__eia_search_routes",
      "mcp__eia-energy__eia_query_route",
      "mcp__eia-energy__eia_dataframe_describe"
    ],
    "ask": [
      "mcp__eia-energy__eia_dataframe_query"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as eia-energy. Review it before you use it.

Capability tags behind 2 rules
  • mcp__eia-energy__eia_browse_routes untrusted-input
  • mcp__eia-energy__eia_dataframe_query private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/eia-energy-mcp-server/verify?hash=e916b4b7877b91bf6d220d03a039b950b79b73e4a2a05241991650eeb1b79059" | jq -e '.changed == false'

Pinned hash e916b4b7877b, from Nov 15, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.cyanheads/eia-energy-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.cyanheads/eia-energy-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cyanheads/eia-energy-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.cyanheads/eia-energy-mcp-server)

Source: MCP Registry · repository. Synced Nov 15, 2026, 04:17 UTC.

eia-energy-mcp-server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the eia-energy-mcp-server safe?

No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the eia-energy-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the eia-energy-mcp-server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the eia-energy-mcp-server have?

6 tools: 1 write, 5 read. eia_dataframe_query, eia_browse_routes, eia_describe_route, eia_search_routes, eia_query_route and eia_dataframe_describe.

Does the eia-energy-mcp-server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the eia-energy-mcp-server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the eia-energy-mcp-server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.