Eco Router
NPM · ECO-ROUTER-MCP
Rank AWS, Google Cloud and Azure regions by grid carbon intensity and latency.
Available components
Last scanned (2 hours ago)
Scores higher than 69% of npm servers
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 940 tokens (~313/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −2
- Stability: pass → 0.83 functional
- 2 Nov 26 0
- Security disclosure: unverified → pass ▲ functional
- 1 Nov 26 0
- Security disclosure: pass → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: pass → unverified ▼ functional
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 22 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/eco-router-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_clean_window Find the cleanest time to run a job ~379
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). Use it when the job can wait; to choose a region, or without a token, use rank_regions. Regions on the same grid zone share one result.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | – | Only consider regions in these countries or groups (EU, EEA), e.g. ["DE", "FR"]. |
| durationHours | integer | yes | How long the job runs, in whole hours (1 to 72). Must not exceed withinHours. |
| energyKwh | number | – | Estimated energy the job uses, in kWh. When set, each option estimates kg CO2e, now and at the best time. |
| limit | integer | – | How many grid zones to return, 1 to 20. Default 5. |
| providers | array | – | Only consider these cloud providers: "aws", "gcp" (Google Cloud), "azure". |
| regions | array | – | Candidate regions as provider/id, e.g. ["aws/eu-north-1", "gcp/europe-west9"]. Tip: shortlist with rank_regions first. All given filters must match. |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| durationHours | integer | yes | Job length used, in hours. |
| evaluatedRegions | integer | yes | Regions that matched the filters. |
| evaluatedZones | integer | yes | Distinct grid zones those regions draw from; each zone is forecast once. |
| generatedAt | string | yes | When this response was computed, ISO 8601 UTC. |
| notes | array | yes | Caveats about data sources, precision and time zones. Pass relevant ones on to the user. |
| results | array | yes | Cleanest grid zones first, at most limit. |
| timezone | string|null | yes | IANA time zone of the local times, or null if unknown. |
| timezoneSource | – | yes | "request" if the caller set timezone, "system" if it is this computer's. |
| unavailable | array | yes | Grid zones skipped because their forecast was missing or too short. |
| withinHours | integer | yes | Deadline used, in hours from now. |
No examples provided.
list_regions List cloud regions ~174
List the cloud regions Eco Router knows about (all public AWS, Google Cloud and Azure regions), with the electricity grid zone each one draws power from. Use it to look up valid region ids, written as provider/id (e.g. aws/eu-north-1), or to check which grid a region uses. Reads bundled data only: no carbon figures, no network calls, no API key. To compare regions by carbon, use rank_regions instead.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Only return regions in this country (ISO 3166-1 alpha-2, e.g. "DE") or group (EU, EEA). Default: all. |
| provider | string | – | Only return regions from this cloud provider: "aws", "gcp" (Google Cloud) or "azure". Default: all. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of regions returned. |
| regions | array | yes | Matching regions, in dataset order. |
No examples provided.
rank_regions Rank cloud regions by carbon ~387
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. Use it to decide where to run; to decide when to start a flexible batch job, use find_clean_window. Works with no setup from annual grid averages; with ELECTRICITY_MAPS_API_TOKEN it uses live grid data, falling back to annual averages per zone. Scores are relative to the regions evaluated. Read `notes` before relying on close scores.
| Name | Type | Req | Description |
|---|---|---|---|
| carbonWeight | number | – | How much carbon counts versus latency, from 0 (latency only) to 1 (carbon only). Default 0.7. Ignored without 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 energy the job uses, in kWh. When set, each result estimates the job's kg CO2e. |
| limit | integer | – | How many regions to return, 1 to 20. Default 5. |
| maxCarbonIntensity | number | – | Exclude regions whose grid is above this carbon intensity, in gCO2e/kWh (e.g. 100). |
| maxLatencyMs | number | – | Exclude regions whose estimated round trip from origin is above this, in milliseconds. Requires origin. |
| origin | object | – | Where the users or data are, e.g. { lat: -27.47, lon: 153.03 } for Brisbane. Enables latency estimates, latency weighting and maxLatencyMs. |
| providers | array | – | Only consider these cloud providers: "aws", "gcp" (Google Cloud), "azure". Default: all. |
| Name | Type | Req | Description |
|---|---|---|---|
| evaluated | integer | yes | Regions that matched the provider and country filters. |
| excluded | object | yes | How many regions each hard limit removed. |
| generatedAt | string | yes | When this response was computed, ISO 8601 UTC. |
| notes | array | yes | Caveats about data sources, precision and time zones. Pass relevant ones on to the user. |
| qualified | integer | yes | Of those, regions that also met maxCarbonIntensity and maxLatencyMs. |
| results | array | yes | Best regions first, at most limit. |
No examples provided.
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.
npm · eco-router-mcp
claude mcp add stevensu04-eco-router-mcp -- npx -y eco-router-mcp
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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 940 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 5 November 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.