MCP.Market

GridHub Electricity Market Data MCP server

online · 100% uptime
by jalcodev·io.github.jalcodev/gridhub·v1.0.2
No reviews yet

Live and historical electricity prices and demand for 25 grids; carbon intensity for GB.

B81/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed GridHub Electricity Market Data yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

GridHub Electricity Market Data tools (6)

write = sends, deletes, buys or posts
  • get_historyFree

    Time series for one metric in one zone over a start/end window (Unix seconds). Rows are returned oldest-first and the 'limit' truncates from the OLDEST end, so a small limit over a wide window returns old data, not recent data — for 'the latest N points' set start close to now, or use get_latest / get_zone_brief for current values. Default window is the last 24h (last ~400 days for capacity, which is annual). Max window 31 days per call (400 for capacity); paginate with start/end for more. Metrics: price (wholesale, local currency per MWh), demand (MW), generation (per fuel, 'fuel' field set; % or MW depending on zone; GB and US-CAISO only), carbon-intensity (gCO2/kWh; GB only), interchange (net imports, MW), capacity (installed MW per fuel; European zones only). Authentication: send 'Authorization: Bearer <ghk_key>' on the MCP connection (free key, 500 requests/day, instant email signup at https://grid-hub.app/developers), or pay per call with x402 (USDC on Base) via the X-PAYMENT header. With no credentials, data tools run in free sample mode: real, current data but truncated (history capped at 50 rows; brief returns one context block). Sample results are clearly marked.

  • get_latestFree

    The most recent value of every metric one zone publishes (price and demand for every zone; generation by fuel for GB and US-CAISO; carbon intensity for GB; interchange where available), each with unit and timestamp. This is the right tool for 'what is the price/demand/carbon intensity in X right now'. Note: some European sources publish day-ahead prices, so the price timestamp can be up to ~36h in the future; use get_zone_brief for a strictly at-or-before-now value with historical context. Authentication: send 'Authorization: Bearer <ghk_key>' on the MCP connection (free key, 500 requests/day, instant email signup at https://grid-hub.app/developers), or pay per call with x402 (USDC on Base) via the X-PAYMENT header. With no credentials, data tools run in free sample mode: real, current data but truncated (history capped at 50 rows; brief returns one context block). Sample results are clearly marked.

  • get_map_snapshotFree

    Current headline values for all 25 zones in one call — the cheapest way to compare zones (e.g. 'which European zone has the lowest price right now', 'rank US ISOs by demand'). Rebuilt every 5 minutes. Authentication: send 'Authorization: Bearer <ghk_key>' on the MCP connection (free key, 500 requests/day, instant email signup at https://grid-hub.app/developers), or pay per call with x402 (USDC on Base) via the X-PAYMENT header. With no credentials, data tools run in free sample mode: real, current data but truncated (history capped at 50 rows; brief returns one context block). Sample results are clearly marked.

  • get_statusFree

    Ingestion health per source and zone: last successful fetch timestamp and last error, if any. Free. Use it to explain stale or missing values before drawing conclusions from them.

  • get_zone_briefFree

    Composite, interpretation-ready snapshot of one zone: current price / demand / carbon intensity where published (strictly at-or-before now), each ranked against that zone's own last ~30 days (percentile, vs-median %, min/max, sample count and the actual data window), a 24h trend per metric, the generation mix where published (GB, US-CAISO), and a one-sentence plain-English summary. Best tool for questions like 'is electricity cheap/clean in X right now' or 'is this a good time to run a flexible workload'. A raw price means little without this context. Authentication: send 'Authorization: Bearer <ghk_key>' on the MCP connection (free key, 500 requests/day, instant email signup at https://grid-hub.app/developers), or pay per call with x402 (USDC on Base) via the X-PAYMENT header. With no credentials, data tools run in free sample mode: real, current data but truncated (history capped at 50 rows; brief returns one context block). Sample results are clearly marked.

  • list_zonesFree

    List the 25 electricity grid zones GridHub covers, with id, name, data source (EIA, ENTSO-E, NESO, AEMO), timezone, currency, licence and required attribution. Free, no credentials needed. Call this first if you are unsure which zone id to use.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 277ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 33 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How GridHub Electricity Market Data compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 62% of 48,243 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
144 ms
faster than 76% of 30,027 servers

What its tools let an agent do: 6 read

Install GridHub Electricity Market Data in Claude Code, Cursor or VS Code

claude mcp add --transport http gridhub https://api.grid-hub.app/mcp
Add to Cursor

What the publisher says

From the GridHub Electricity Market Data repository's README, as published. We do not edit it. Read it on GitHub

GridHub MCP Server

Live and historical electricity market data for AI agents, over the Model Context Protocol.

Endpoint: https://api.grid-hub.app/mcp — hosted, Streamable HTTP, stateless. Nothing to install.

Covers 25 grid zones — US ISOs (CAISO, ERCOT, PJM, MISO, NYISO, ISO-NE, SPP), 12 European bidding zones, Great Britain, and the five Australian NEM regions — normalised into one JSON schema. Sourced from EIA, ENTSO-E, NESO, Elexon and AEMO; every response carries its licence and attribution.

Tools

Access

Three levels, no signup needed to start:

  1. Sample mode — connect with no credentials. Tools return real, current data, truncated (history capped at 50 rows; brief returns one context block). Results are clearly marked.
  2. Free API key — 500 requests/day. Instant email signup at grid-hub.app/developers, or POST https://api.grid-hub.app/v1/keys/signup with {"email": "..."}. Send as Authorization: Bearer .
  3. x402 pay-per-call — USDC on Base, $0.001–$0.02 per call, via the X-PAYMENT header. See the x402 flow.

Setup

Claude Code

claude mcp add --transport http gridhub https://api.grid-hub.app/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Cursor / Windsurf / VS Code (mcp.json)

{
  "mcpServers": {
    "gridhub": {
      "url": "https://api.grid-hub.app/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Claude Desktop / claude.ai — add https://api.grid-hub.app/mcp as a custom connector. These clients don't send custom headers; pass the key as the optional api_key tool argument, or use sample mode.

Local stdio bridge — for clients that only support local (stdio) servers. It proxies to the hosted endpoint via mcp-remote; nothing runs locally except the bridge.

{
  "mcpServers": {
    "gridhub": {
      "command": "npx",
      "args": ["-y", "github:jalcodev/gridhub-mcp"],
      "env": { "GRIDHUB_API_KEY": "YOUR_KEY" }
    }
  }
}

Or with Docker: docker build -t gridhub-mcp . && docker run -i -e GRIDHUBAPIKEY=YOUR_KEY gridhub-mcp. Omit the key for sample mode.

Any client, no key — omit the header. You'll get sample-mode data and a note on how to upgrade.

Protocol

  • Streamable HTTP, stateless: one JSON-RPC message per POST, JSON response. No sessions, no SSE.
  • Speaks MCP 2026-07-28 (header-mirrored requests, no handshake) and 2025-03-26 through 2025-11-25 (initialize handshake).
  • Tool results include structuredContent alongside the text block.
  • Rate limits and quotas are those of the underlying REST API; the MCP layer adds none of its own.

Related

  • REST API docs: https://grid-hub.app/developers
  • OpenAPI: https://api.grid-hub.app/openapi.json
  • llms.txt: https://api.grid-hub.app/llms.txt
  • Official MCP Registry entry: io.github.jalcodev/gridhub

License

The code in this repository is MIT licensed. Data returned by the service is subject to each source's licence, stated in every response (license and attribution fields).

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-30downgradeA → Bscore 81

GridHub Electricity Market Data: common questions

Is GridHub Electricity Market Data MCP server safe?
Mostly: it is graded B (81/100). Read the GridHub Electricity Market Data safety report
How do I install GridHub Electricity Market Data?
It runs remotely at api.grid-hub.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does GridHub Electricity Market Data need an API key?
Yes. The registry entry asks for Authorization.
Is GridHub Electricity Market Data maintained?
The last commit was 39 days ago (2026-09-27). The latest release is v1.0.2.
Is GridHub Electricity Market Data up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does GridHub Electricity Market Data compare with other MCP servers?
safety score 81/100 (higher than 62% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.