Skip to main content
Glama

Related Servers

Alternatives to eco-router-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      2
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables querying of real-time and forecast UK carbon intensity data from National Grid ESO, allowing AI agents to retrieve carbon emissions by region and time.
      2 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Carbon-aware MCP scheduler that defers "do it later" / "by tomorrow" / "overnight" LLM tasks to the cleanest electricity-grid hour inside a deadline — 40-70% lower CO2 per task, 50% cheaper via Anthropic/OpenAI Batch APIs. 9 MCP tools, per-task carbon receipts to local SQLite, Apache-2.0.
      1
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to query current and historical UK electricity carbon intensity, generation mix, and regional intensity data to schedule energy-intensive tasks during low-carbon periods.
      1 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query verified-emissions knowledge graphs in natural language and validate data against supported standards, with metered billing and optional verified identity.
      16
      824 npm
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing known regions, ranking regions for a workload, and finding optimal start times for batch jobs. There is no overlap in what they return or when an agent would choose one over another.

    Naming Consistency5/5

    All three tool names follow a consistent verb_noun pattern: list_regions, rank_regions, find_clean_window. The verbs clearly indicate the action and the nouns indicate the object.

    Tool Count4/5

    Three tools is on the low end, but the server has a focused purpose: carbon-aware region selection. Each tool covers a distinct stage of that workflow, so the count feels appropriate rather than thin.

    Completeness4/5

    The tool surface covers the core workflow: discover regions, rank them for a workload, and find clean windows for flexible jobs. A minor gap is the lack of a tool to fetch detailed grid data for a single region, but agents can work around it with list_regions and rank_regions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues