
Georgia Energy MCP server
online · 100% uptimeGeorgia (country) electricity system — live grid telemetry and regulator statistics.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Georgia Energy yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Georgia Energy tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Georgia Energy compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 39% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 477 ms
- faster than 31% of 30,031 servers
Release history: 6 versions in the registry since 2026-09-16, latest 2026-11-02, typically one every 4 days.
Install Georgia Energy in Claude Code, Cursor or VS Code
claude mcp add --transport http georgia-energy https://gateway.pipeworx.io/georgia-energy/mcp
What the publisher says
From the Georgia Energy repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/georgia-energy
Georgia's (the country's) national electricity system: live grid telemetry from the transmission system operator, and the regulator's per-power-station monthly generation and price series.
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tools
hydro / thermal / wind / solar generation, total generation, cross-border flow on the Azerbaijan, Armenia, Russia (with the Salkhino, Java and Nakaduli lines broken out) and Turkey tie lines, and total consumption, in MW.
- gsegridnow(...) — the grid as of the latest published 3-minute slot:
rolling ~30-day retention window.
- gsegridat(...) — the same blocks for one explicit past slot, inside the
How far it sits from 50 is a direct read on generation-versus-demand balance.
- gse_frequency(...) — system frequency in Hz (nominal 50), 1-minute feed.
supply, thermal, hydro (regulated and seasonal), wind, import and export.
- gsedemandforecast(...) — the day-ahead forecast, hour by hour: consumption,
Generation Adequacy Assessment, annual reports and the SESA.
- gse_publications(...) — the operator's reports and notices, including the
and bid prices where published.
- gse_tenders(...) — the operator's procurement tenders with awarded bidders
stations (Enguri, the Vardnili cascade, Khrami 1/2, Zhinvali, Gardabani thermal 1/2, the Kartli wind farm, named solar plants) plus national supply, consumption, import, export and named large direct consumers, 2015-2026.
- gnercstationgeneration(...) — monthly generation for individual power
fee, and the price ESCO paid deregulated stations, 2015-2026.
- gnerc_prices(...) — monthly balancing-electricity price, guaranteed-capacity
Auth
Keyless. No token, no cookie, no registration on either publisher.
Data sources
Electrosystem (GSE) real-time system exports. GSEEXPORTNEWPERIOD03M.XML every 3 minutes, GSEEXPORTPERIOD01M_*.XML (frequency) every minute.
- — JSC Georgian State
probe for the above. Verified to discriminate correctly in both directions. — the operator's Laravel content API. meta.total is a genuine total. — day-ahead consumption forecast.
- — GSE's own existence
Regulatory Commission (GNERC) open-data workbooks.
- — Georgian National Energy and Water Supply
Things that will otherwise be rediscovered the hard way
GSE filenames are in Tbilisi local time (UTC+4), not UTC, with the minute floored to a multiple of 3, and publication lags. Asking for the current minute returns a 404, not an error — so "now" must mean "the newest slot that exists", which is why every read walks backwards and proves the slot with file-exists first. The lag is not the ~2 minutes the original sample suggested: the 1-minute frequency feed has been observed 9-10 slots behind. That is why the walk probes in concurrent batches — ten sequential round trips to Tbilisi cost about four seconds, most of it waiting.
Every telemetered value carries a QUALITY attribute and most of them are not measurements. ACT is actual telemetry; SUB was substituted by the operator; NRE was not received. A representative live export had 3 ACT, 7 SUB and 3 NRE — national consumption was NRE and the hydro total SUB. So the flag travels with every row and is summarised at the top of the response. Dropping it would return a fill-in as a measurement, which is worse than returning nothing.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Georgia Energy: common questions
- Is Georgia Energy MCP server safe?
- Mostly: it is graded B (73/100). Read the Georgia Energy safety report
- How do I install Georgia Energy?
- It runs remotely at gateway.pipeworx.io. 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 Georgia Energy need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Georgia Energy maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.2.1.
- Is Georgia Energy up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Georgia Energy compare with other MCP servers?
- safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 477 ms (faster than 31% of 30,031 servers). Full comparison.