Eco Router
NPM · ECO-ROUTER-MCP · SCANNED SEP 20
Rank AWS, Google Cloud and Azure regions by grid carbon intensity and latency.
Available components
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 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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.
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
{
"mcpServers": {
"stevensu04-eco-router-mcp": {
"command": "npx",
"args": [
"-y",
"eco-router-mcp"
]
}
}
} {
"servers": {
"stevensu04-eco-router-mcp": {
"command": "npx",
"args": [
"-y",
"eco-router-mcp"
]
}
}
} codex mcp add stevensu04-eco-router-mcp -- npx -y eco-router-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stevensu04-eco-router-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"eco-router-mcp"
],
"enabled": true
}
}
} openclaw mcp add stevensu04-eco-router-mcp --command npx --arg -y --arg eco-router-mcp
mcp_servers:
stevensu04-eco-router-mcp:
command: "npx"
args: ["-y", "eco-router-mcp"] {
"McpServers": {
"stevensu04-eco-router-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"eco-router-mcp"
]
}
}
} assistant mcp add stevensu04-eco-router-mcp -t stdio -c npx -a -y eco-router-mcp
{
"mcpServers": {
"stevensu04-eco-router-mcp": {
"command": "npx",
"args": [
"-y",
"eco-router-mcp"
]
}
}
} 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.
- 17 Sept 26 70
First indexed and scored.
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 20 Sept 2026 · Analysed npm/eco-router-mcp@0.1.0
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 ~282
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).
| Name | Type | Req | Description |
|---|---|---|---|
| countries | array | – | Only consider regions in these countries or groups (EU, EEA). |
| durationHours | integer | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| durationHours | integer | yes | – |
| evaluatedRegions | integer | yes | – |
| evaluatedZones | integer | yes | – |
| generatedAt | string | yes | – |
| notes | array | yes | – |
| results | array | yes | – |
| timezone | string|null | yes | – |
| timezoneSource | – | yes | – |
| unavailable | array | yes | – |
| withinHours | integer | yes | – |
No examples provided.
list_regions List cloud regions ~79
List the cloud regions Eco Router knows about, with the electricity grid zone each one draws power from.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| regions | array | yes | – |
No examples provided.
rank_regions Rank cloud regions by carbon ~238
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| evaluated | integer | yes | – |
| excluded | object | yes | – |
| generatedAt | string | yes | – |
| notes | array | yes | – |
| qualified | integer | yes | – |
| results | array | yes | – |
No examples provided.
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.