Skip to main content
Glama

Server Details

Energy-Charts (Fraunhofer ISE) MCP — European electricity generation, prices, and capacity.

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
44.0% over 39 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-energy-charts
GitHub Stars
0
Server Listing
Energy Charts MCP

TDQS

A3.9/5.0

Scored across 37 tools

Disambiguation3/5

Most tools have distinct purposes, but there are clear overlap clusters: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded (beta is explicitly described as 'identical' to the stable router), and the energy set (public_power, total_power, generation_mix, installed_power, renewable_share) where multiple tools all return generation-by-production-type and are easy to confuse. The Polymarket family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) is well differentiated by descriptions, but the router trio and energy trio create real misselection risk.

Naming Consistency4/5

Names are consistently snake_case throughout, with a mix of verb_noun (resolve_entity, compare_entities, discover_tools, validate_claim) and noun_verb/domain-noun (electricity_price, generation_mix, polymarket_edges). Single-verb tools (recall, remember, forget, subscribe, unsubscribe) are coherent verbs, so the overall pattern is predictable with only minor stylistic variation.

Tool Count2/5

37 tools is heavy and far above the well-scoped range, and the count is mismatched to the server name 'Energy Charts' — only about five tools are actually energy-related. Although the gateway's fan-out meta-tools (ask_pipeworx, entity_profile, deep_research) reduce the need for many granular tools, the large multi-domain surface and router variants feel bloated rather than earned.

Completeness4/5

As an aggregator surface it covers a wide domain well: energy (price, mix, capacity, totals, renewables), entity resolution/profiling, prediction markets end-to-end (discovery, edges, tracking, fill risk, cross-venue), plus memory, subscriptions, and self-improvement tools. The main gap is that coverage is generic-gateway broad rather than a coherent 'Energy Charts' lifecycle (no forecasting/emissions tooling despite being energy-named), but operational dead ends are largely avoided.

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

  • A
    license
    B
    quality
    A
    maintenance
    Provides real-time European and GB electricity grid data via MCP, including generation, prices, carbon intensity, and grid infrastructure.
    44
    21 npm
    6
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for querying ENTSO-E Transparency Platform data including actual load, generation per type, cross-border flows, and installed capacity.
    1 npm
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    MCP server for Swiss electricity data from three official sources — production mix, consumption forecast, storage-lake fill, consumer price index, tariffs per municipality, and dataset discovery. Zero authentication.
    12
    19 PyPI
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    MCP server for real-time electricity prices, carbon intensity, and energy analytics across 41+ zones in Europe, Great Britain, the United States, and Australia. Query live prices, compare zones, check gas storage levels, get green scores, find optimal charging windows, and access advanced analytics. Free Basic tier requires no API key. Install via npx gridpulse-mcp or connect directly via Streamab
    -
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.