Skip to main content
Glama

Eia

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

EIA MCP — US Energy Information Administration API v2

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
42.3% over 40 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-eia
GitHub Stars
0
Server Listing
eia

TDQS

A3.8/5.0

Scored across 36 tools

Disambiguation3/5

Most tool families are distinguishable (EIA energy tools, Polymarket tools, meta/subscription tools), but the router family is genuinely overlapping: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same 5,961 tools, with beta explicitly admitting it currently matches stable exactly. Entity tools (resolve_entity / entity_profile / compare_entities / recent_changes) also tread close to each other, though their descriptions draw usable boundaries.

Naming Consistency3/5

Everything is snake_case, which is consistent at the character-style level, but the construction is mixed: verb-phrase names (ask_pipeworx, resolve_entity, validate_claim, discover_tools, scan_dependency), noun-phrase names (entity_profile, recent_changes, recent_alerts, list_subscriptions, ai_visibility_check), and source-prefixed names (eia_*, polymarket_*). Readable but no single predictable pattern.

Tool Count3/5

36 tools is heavy for a single MCP connection and leans past the comfortable range, yet a broad multi-source gateway legitimately needs separate families for routing, EIA energy data, prediction markets, entity resolution, and subscription management. The count would be more defensible without the redundant ask_pipeworx beta/stable pair and the many Polymarket siblings.

Completeness4/5

The surface is broadly complete for a data gateway: routing (ask/grounded/deep_research), discovery, entity resolution, profiles, comparison, validation, memory (remember/recall/forget), subscriptions (subscribe/list/unsubscribe), alerts, feedback, and trending are all present. Minor gaps remain (no quota/usage tool, EIA coverage is narrow), but few dead ends for an agent.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

  • @cyanheads/eia-energy-mcp

    cyanheads
    A
    license
    Not graded
    quality
    A
    maintenance
    Browse and query the U.S. Energy Information Administration API v2 — electricity, petroleum, natural gas, coal, forecasts, and more via MCP. STDIO or Streamable HTTP.
    258 npm
    2
    Apache 2.0

  • mcp-server-eia

    GSA-TTS
    F
    license
    A
    quality
    C
    maintenance
    An MCP server that exposes the U.S. Energy Information Administration (EIA) Open Data API, enabling LLMs to browse and query energy data across 17 datasets with generic, composable tools.
    4
    -

  • aemo-mcp

    Bigred97
    A
    license
    A
    quality
    B
    maintenance
    One-call Australian energy-market plumbing via AEMO — cited, structured responses for market data and analysis, not a data broker.
    5
    130 PyPI
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources