GridHub Electricity Market Data MCP Server

by jalcodev Your server? Claim it

answering

GridHub Electricity Market Data is answering right now. Last checked 8 min ago. It exposes 6 tools. Last commit 27 Sep 2026.

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

Uptime history 49 days of history · worst day 92%

49 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

106 ms

Response time

average over 24h

Stars

last commit 27 Sep 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 August 2026. No other catalogue keeps this.

29 Aug 4 tool descriptions were rewritten get_history, get_latest, get_map_snapshot and 1 more

What the code does

We read the source, 1 d ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command bin/gridhub-mcp.mjs:19

const child = spawn(process.execPath, [bin, ...args], { stdio: "inherit" });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "gridhub": {
      "url": "https://api.grid-hub.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.gridhub]
url = "https://api.grid-hub.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "gridhub": {
      "url": "https://api.grid-hub.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "gridhub": {
      "url": "https://api.grid-hub.app/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

history

get_history

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.

latest

get_latest

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.

map

get_map_snapshot

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.

status

get_status

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.

zone

get_zone_brief

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.

zones

list_zones

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.

Endpoints

URL	Transport	State	Latency	Checked
https://api.grid-hub.app/mcp	streamable-http	answering	75 ms	8 min ago

Alternatives to GridHub Electricity Market Data

same job, measured the same way

Electricity Maps

by pipeworx-io

Electricity Maps MCP — real-time electricity-grid carbon intensity + power

43 tools answering

Iso Ne

by pipeworx-io

Real-time power grid data for ISO New England, the electricity market and grid operator for…

43 tools answering

Eia MCP Gridsense

by pranavbhosale25

MCP server for US electricity grid data: fuel mix, demand, retail prices, CO2 emissions

95 installs/wk local only

Grid Carbon MCP

by nexlab

Electricity grid carbon intensity for Great Britain from the National Grid ESO Carbon Intensity API

answering

Ticker: Live Event Ticket Market

by findticker

Live event ticket market data: prices, inventory, demand and seat maps, with screens and alerts.

answering

Pjm

by pipeworx-io

Real-time electricity market data from PJM Interconnection, the largest US grid operator (13…

44 tools answering

Inferenceindexer MCP

by desmartin01

AI inference pricing for agents: live and historical model prices, provider comparison.

125 installs/wk 10 tools answering

Gridcarbon MCP

by gridcarbon

Hourly electricity carbon intensity for 45 zones, from ENTSO-E, EIA and NESO. No API key needed.

21 installs/wk local only

GridHub Electricity Market Data — questions

Answers built from our own checks of this server.

What can GridHub Electricity Market Data do?

It exposes 6 tools, read directly from the server on our last check. Among them: get_history, get_latest, get_map_snapshot, get_status, get_zone_brief, list_zones. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is GridHub Electricity Market Data working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 106 ms. The bar chart above shows every period we have measured.

How do I connect GridHub Electricity Market Data?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does GridHub Electricity Market Data need an API key?

No. GridHub Electricity Market Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is GridHub Electricity Market Data?

It answers our handshake in 106 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is GridHub Electricity Market Data open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.