# Eco Router (npm · eco-router-mcp)

Rank AWS, Google Cloud and Azure regions by grid carbon intensity and latency.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `eco-router-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/stevensu04-eco-router-mcp/eco-router-mcp.md), [page](https://verifymcp.io/servers/stevensu04-eco-router-mcp/eco-router-mcp)

## Channel facts

- Registry: `npm`
- Package: `eco-router-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 599 tokens (~199/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Eco Router MCP server?

Eco Router runs locally as an npm package, launched with npx -y eco-router-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add stevensu04-eco-router-mcp -- npx -y eco-router-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "stevensu04-eco-router-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eco-router-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stevensu04-eco-router-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eco-router-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add stevensu04-eco-router-mcp -- npx -y eco-router-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stevensu04-eco-router-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "eco-router-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stevensu04-eco-router-mcp --command npx --arg -y --arg eco-router-mcp
```

### Hermes

```yaml
mcp_servers:
  stevensu04-eco-router-mcp:
    command: "npx"
    args: ["-y", "eco-router-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "stevensu04-eco-router-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "eco-router-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add stevensu04-eco-router-mcp -t stdio -c npx -a -y eco-router-mcp
```

### Other

```json
{
  "mcpServers": {
    "stevensu04-eco-router-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eco-router-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-17 (score 70)

First indexed and scored.

## MCP tools (3)

### `list_regions` (~79 tokens)

List cloud regions

List the cloud regions Eco Router knows about, with the electricity grid zone each one draws power from.

Input parameters:

- `country` (string): Only return regions in this country (ISO 3166-1 alpha-2, e.g. "DE") or group (EU, EEA).
- `provider` (string): Only return regions from this cloud provider.

Output parameters:

- `count` (integer)
- `regions` (array)

### `rank_regions` (~238 tokens)

Rank cloud regions by carbon

Rank AWS, Google Cloud and Azure regions for a workload by the carbon intensity of their electricity grid, optionally balanced against estimated latency from an origin. Supports hard limits for allowed countries, maximum latency and maximum carbon intensity. Read `notes` before relying on close scores.

Input parameters:

- `carbonWeight` (number): Weight on carbon versus latency, 0..1. Default 0.7. Only used with origin.
- `countries` (array): Only consider regions in these countries or groups (EU, EEA), e.g. ["EU"] for EU data residency. Default: all.
- `energyKwh` (number): Estimated job energy, to report emissions per region.
- `limit` (integer): How many regions to return. Default 5.
- `maxCarbonIntensity` (number): Exclude regions above this carbon intensity, gCO2e/kWh.
- `maxLatencyMs` (number): Exclude regions estimated slower than this round trip. Requires origin.
- `origin` (object): Where users or data are. Enables latency estimates and latency weighting.
- `providers` (array): Only consider these cloud providers. Default: all.

Output parameters:

- `evaluated` (integer)
- `excluded` (object)
- `generatedAt` (string)
- `notes` (array)
- `qualified` (integer)
- `results` (array)

### `find_clean_window` (~282 tokens)

Find the cleanest time to run a job

For flexible batch jobs, find when in the next hours (up to 72) each candidate region's grid is forecast to be cleanest, and how much that saves compared with starting now. Local times default to this computer's time zone. Needs ELECTRICITY_MAPS_API_TOKEN with forecast access. Limit candidates with regions, providers or countries (at most 15 grid zones per call).

Input parameters:

- `countries` (array): Only consider regions in these countries or groups (EU, EEA).
- `durationHours` (integer, required): How long the job runs, in whole hours.
- `energyKwh` (number): Estimated job energy, to report emissions for each option.
- `limit` (integer): How many options to return. Default 5.
- `providers` (array): Only consider these cloud providers.
- `regions` (array): Candidate regions as provider/id, e.g. ["aws/eu-north-1", "gcp/europe-west9"]. Tip: shortlist with rank_regions first.
- `timezone` (string): IANA time zone for local start times, e.g. "Australia/Brisbane". Defaults to the time zone of the computer running Eco Router; set it when the user is elsewhere.
- `withinHours` (integer): The job must finish within this many hours from now. Default 24, max 72.

Output parameters:

- `durationHours` (integer)
- `evaluatedRegions` (integer)
- `evaluatedZones` (integer)
- `generatedAt` (string)
- `notes` (array)
- `results` (array)
- `timezone` (string|null)
- `timezoneSource`
- `unavailable` (array)
- `withinHours` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/stevensu04-eco-router-mcp/eco-router-mcp#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 70

## Common questions

### What is the Eco Router MCP server?

Eco Router is an MCP server listed in the public MCP registry as io.github.stevensu04/eco-router-mcp. Rank AWS, Google Cloud and Azure regions by grid carbon intensity and latency. This page covers its npm package (eco-router-mcp).

### Is the Eco Router MCP server safe to use?

Eco Router scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Eco Router MCP server expose?

Eco Router exposes 3 tools: list_regions, rank_regions, find_clean_window. Their descriptions and schemas cost roughly 599 tokens of context every time the server is loaded.

### Is the Eco Router MCP server still maintained?

Eco Router is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Eco Router MCP server under?

Eco Router declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/eco-router-mcp
- Socket report: https://socket.dev/npm/package/eco-router-mcp
- Repository: https://github.com/stevensu04/eco-router-mcp
- Changelog RSS feed: https://verifymcp.io/servers/stevensu04-eco-router-mcp/eco-router-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/stevensu04-eco-router-mcp/eco-router-mcp.json
- HTML version of this page: https://verifymcp.io/servers/stevensu04-eco-router-mcp/eco-router-mcp