gridhub-mcp
Related Servers
Alternatives to gridhub-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP 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-
- AlicenseNot gradedqualityBmaintenanceProvides real-time grid carbon intensity, power generation breakdown, and carbon-intensity forecasts for any zone or lat/lon location.21 npmMIT
- AlicenseAqualityDmaintenanceProvides real-time electricity grid data including CO2 intensity, power mix, and wholesale prices, plus optimal green time windows for energy-intensive AI tasks. Supports UK, Germany, and global regions with optional API keys.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to pull US ZIP-code-level electricity data — Scope 2 location- and market-based emission factors, Scope 1 fuel factors, hourly grid carbon intensity, plant-level emissions, retail rates, and utility tariffs — for carbon accounting, multi-site comparison, and finding the cleanest hours to run flexible loads. It requires no API key or signup and works as either a hosted remote endpoint or a local stdio process.1MIT

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- AlicenseNot gradedqualityCmaintenanceEnables access to real-time electricity data for a 15-state US region plus Manitoba: fuel mix, five-minute wholesale prices, binding transmission constraints, load and forecasts, and wind/solar output. Can run as a remote MCP endpoint or a local stdio server with no authentication.13 npmMIT
TDQS
Scored across 6 tools
The tools are mostly distinct: list_zones covers metadata, get_map_snapshot covers cross-zone current values, get_status covers health, get_history covers time series, and get_zone_brief adds interpretation. get_latest and get_zone_brief both address current conditions, but the descriptions clearly differentiate raw latest values from contextual at-or-before-now snapshots.
All tool names follow a clear list_/ get_ verb pattern with a descriptive object, such as list_zones, get_status, and get_history. There is no mixed casing or inconsistent verb style, making the set predictable and easy to navigate.
Six tools is a well-scoped size for a read-only electricity grid data server. Each tool covers a distinct need: discovery, health, raw latest values, interpreted snapshot, history, and cross-zone comparison, so no tool feels redundant or extraneous.
The set covers the full read-only data lifecycle for this domain: zone metadata, ingestion health, current raw values, contextual interpretation, historical series, and multi-zone comparison. There are no obvious dead ends or missing operations that would block an agent from answering common questions about grid data.