Georgia Energy
Server Details
Georgia (country) electricity system — live grid telemetry and regulator statistics.
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
- 0.3% over 25 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-georgia-energy
- GitHub Stars
- 0
- Server Listing
- georgia-energy
TDQS
Scored across 44 tools
The descriptions are extremely explicit about when to use which tool (e.g. ask_pipeworx vs ask_pipeworx_grounded vs deep_research, entity_profile vs company_facts vs recent_changes), which rescues a surface that has real conceptual overlap. Still, four near-identical 'ask_pipeworx*' routers, five overlapping polymarket trade tools, and several company-profile tools create genuine misselection risk, and the server name ('Georgia Energy') gives no clue that the set is a broad data gateway.
All 44 names are snake_case and mostly follow verb_noun or clear noun-phrase patterns (resolve_entity, validate_claim, entity_profile, polymarket_fill_risk), grouped by coherent prefixes (gse_, gnerc_, polymarket_, ask_pipeworx_). Minor deviations like ai_visibility_check (noun_verb) and the _beta suffix are readable and not chaotic.
At 44 tools the set is heavy, and it is far broader than the server's stated 'Georgia Energy' purpose — only 8 tools (gse_*/gnerc_*) relate to Georgia's grid, while the rest span SEC filings, FDA, prediction markets, memory, and subscriptions. That is a large surface for a single MCP connection and the scope mismatch means many tools will never be relevant to the nominal domain.
Coverage is unusually deep for the domains it touches: Georgia grid data spans prices, station generation, demand forecast, frequency, real-time and historical grid state, publications and tenders; entity resolution, comparison, verification and memory/subscription lifecycles are each complete enough for real workflows. Gaps are modest (e.g. gse_grid_at limited to a rolling ~30 days, no station-level real-time stream), but agents can work around them.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
release_calendar_markets2 fields changed- added
Output schema / properties / empty_reasonAdded value: +{ + "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.", + "type": "string" +} - added
Output schema / properties / hintAdded value: +{ + "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).", + "type": "string" +}
7 tool updates
- Changed
ask_pipeworx3 fields changed- added
Input schema / properties / askAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / messageAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - changed
Input schema / properties / question / descriptionPrevious value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
- Changed
ask_pipeworx_beta3 fields changed- added
Input schema / properties / askAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / messageAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - changed
Input schema / properties / question / descriptionPrevious value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
- Changed
ask_pipeworx_grounded3 fields changed- added
Input schema / properties / askAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / messageAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - changed
Input schema / properties / question / descriptionPrevious value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."
- Changed
deep_research8 fields changed- added
Input schema / properties / askAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / inputAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / messageAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / promptAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / qAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - added
Input schema / properties / queryAdded value: +{ + "description": "Alias for question.", + "type": "string" +} - changed
Input schema / properties / question / descriptionPrevious value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases." - added
Input schema / properties / textAdded value: +{ + "description": "Alias for question.", + "type": "string" +}
- Changed
forget4 fields changed- added
Input schema / properties / kAdded value: +{ + "description": "Alias for key.", + "type": "string" +} - changed
Input schema / properties / key / descriptionPrevious value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases." - added
Input schema / properties / labelAdded value: +{ + "description": "Alias for key.", + "type": "string" +} - added
Input schema / properties / nameAdded value: +{ + "description": "Alias for key.", + "type": "string" +}
- Changed
recall4 fields changed- added
Input schema / properties / kAdded value: +{ + "description": "Alias for key.", + "type": "string" +} - changed
Input schema / properties / key / descriptionPrevious value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases." - added
Input schema / properties / labelAdded value: +{ + "description": "Alias for key.", + "type": "string" +} - added
Input schema / properties / nameAdded value: +{ + "description": "Alias for key.", + "type": "string" +}
- Changed
remember9 fields changed- added
Input schema / properties / contentAdded value: +{ + "description": "Alias for value.", + "type": "string" +} - added
Input schema / properties / dataAdded value: +{ + "description": "Alias for value.", + "type": "string" +} - added
Input schema / properties / kAdded value: +{ + "description": "Alias for key.", + "type": "string" +} - changed
Input schema / properties / key / descriptionPrevious value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases." - added
Input schema / properties / labelAdded value: +{ + "description": "Alias for key.", + "type": "string" +} - added
Input schema / properties / nameAdded value: +{ + "description": "Alias for key.", + "type": "string" +} - added
Input schema / properties / textAdded value: +{ + "description": "Alias for value.", + "type": "string" +} - added
Input schema / properties / vAdded value: +{ + "description": "Alias for value.", + "type": "string" +} - changed
Input schema / properties / value / descriptionPrevious value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."
44 tool updates
- First observed
ai_visibility_check - First observed
ask_pipeworx - First observed
ask_pipeworx_beta - First observed
ask_pipeworx_grounded - First observed
bet_research - First observed
company_facts - First observed
compare_entities - First observed
deep_research - First observed
discover_tools - First observed
entity_profile - First observed
forget - First observed
generate_llms_txt - First observed
gnerc_prices - First observed
gnerc_station_generation - First observed
gse_demand_forecast - First observed
gse_frequency - First observed
gse_grid_at - First observed
gse_grid_now - First observed
gse_publications - First observed
gse_tenders - First observed
kalshi_weather_edge - First observed
list_subscriptions - First observed
pipeworx_feedback - First observed
pipeworx_trending - First observed
polymarket_arbitrage - First observed
polymarket_edge_tracker - First observed
polymarket_edges - First observed
polymarket_fill_risk - First observed
polymarket_kalshi_spread - First observed
recall - First observed
recent_alerts - First observed
recent_changes - First observed
release_calendar_markets - First observed
remember - First observed
resolution_audit - First observed
resolution_diff - First observed
resolve_entity - First observed
scan_competitor_ai_presence - First observed
scan_dependency - First observed
search_within - First observed
subscribe - First observed
suggest_questions - First observed
unsubscribe - First observed
validate_claim
Related MCP Connectors
Live U.S. electric-grid data, forecasts, alerts, and analysis across major grid regions.
Live and historical electricity prices and demand for 25 grids; carbon intensity for GB.
Real-time power grid data for ISO New England, the electricity market and grid operator for…
Real-time electricity market data from PJM Interconnection, the largest US grid operator (13…
Related MCP Servers
- AlicenseAqualityBmaintenanceLive and historical electricity prices, demand, generation mix and carbon intensity for 25 grid zones (US, Europe, GB, Australia). Hosted endpoint plus local stdio bridge; free sample mode, free API key, or x402 pay-per-call.6MIT

gridcarbon-mcpofficial
AlicenseAqualityFmaintenanceHourly electricity grid carbon intensity (gCO2eq/kWh) for 45 zones across Europe, the US and Great Britain, computed from ENTSO-E, EIA and NESO generation data. Four read-only tools; every value carries its interval timestamp and how stale it is. No API key, no account.4MIT- AlicenseBqualityAmaintenanceProvides real-time European and GB electricity grid data via MCP, including generation, prices, carbon intensity, and grid infrastructure.44165 npm6MIT
- AlicenseNot gradedqualityDmaintenanceProvides real-time US power grid intelligence and carbon intensity data to enable carbon-aware AI compute scheduling across major grid regions. It allows users to monitor energy generation and optimize workloads based on renewable energy availability and grid load forecasts.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.