io.github.CloudCorpRecords/wattindex
NPM · @RENETURCIOS/WATTINDEX · 2 COMPONENTS
GPU energy per million output tokens by model and GPU, with grid carbon intensity.
Available components
Last scanned (8 hours ago)
Scores higher than 31% of npm servers
Category AI and Machine Learning
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 571 tokens (~71/item across 8 items; 8 tools + 0 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 49
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 5 Nov 2026 · Analysed npm/@reneturcios/wattindex@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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
compare_gpus ~61
Compare the best energy rows for a model on H100 versus B200.
| Name | Type | Req | Description |
|---|---|---|---|
| itl_deadline_ms | number | – | Latency ceiling in milliseconds for choosing the best row (default 500) |
| model | string | yes | Model name on the index |
No output schema declared.
No examples provided.
concurrency_curve ~46
Return energy per million tokens at every measured running batch for a model on a GPU.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | yes | GPU name |
| model | string | yes | Model name on the index |
No output schema declared.
No examples provided.
energy_per_million_tokens ~96
Return the best energy row per GPU for a model: watt-hours per million output tokens, keeping rows at or under the inter-token latency deadline.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | GPU name; omit to get the best row for every GPU |
| itl_deadline_ms | number | – | Latency ceiling in milliseconds for choosing the best row (default 500) |
| model | string | yes | Model name on the index |
No output schema declared.
No examples provided.
estimate ~219
Estimate GPU energy for a token count from the best matching row, with kg CO2e for a grid and optional energy at the meter.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name, short name, ISO 3166 alpha-2/alpha-3 code, or World |
| gpu | string | – | GPU name; omit to use the best row overall |
| itl_deadline_ms | number | – | Latency ceiling in milliseconds for choosing the best row (default 500) |
| model | string | yes | Model name on the index |
| num_gpus | integer | – | Only configurations on exactly this many GPUs |
| output_tokens | number | yes | Number of output tokens to price |
| pue | number | – | Power usage effectiveness, at least 1.0; enables energy at the meter |
| running_batch | number | – | Average running batch; the measured configuration nearest to it is used |
| system_power_ratio | number | – | Whole-system to GPU power ratio, at least 1.0; enables energy at the meter |
No output schema declared.
No examples provided.
gpu_hardware ~45
Return GPU hardware specs: max TDP, memory, MIG profiles and whole-system ceilings.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | GPU name; omit to list every GPU on the index |
No output schema declared.
No examples provided.
grid_intensity ~59
Return the annual average grid carbon intensity (gCO2e per kWh) for a country or World.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country name, short name, ISO 3166 alpha-2/alpha-3 code, or World |
No output schema declared.
No examples provided.
list_models ~23
List the models on the index and the GPUs each model has measurements for.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sources ~22
List every source behind the index, with version, retrieval date and licence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/wattindex MCP server?
io.github.CloudCorpRecords/wattindex runs locally as an npm package, launched with npx -y @reneturcios/wattindex. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/wattindex
claude mcp add cloudcorprecords-wattindex -- npx -y @reneturcios/wattindex
What is the io.github.CloudCorpRecords/wattindex MCP server?
io.github.CloudCorpRecords/wattindex is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/wattindex. GPU energy per million output tokens by model and GPU, with grid carbon intensity. This page covers its npm package (@reneturcios/wattindex).
Is the io.github.CloudCorpRecords/wattindex MCP server safe to use?
io.github.CloudCorpRecords/wattindex scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 io.github.CloudCorpRecords/wattindex MCP server expose?
io.github.CloudCorpRecords/wattindex exposes 8 tools: list_models, energy_per_million_tokens, estimate, compare_gpus, concurrency_curve, and 3 more. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/wattindex MCP server still maintained?
io.github.CloudCorpRecords/wattindex 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 io.github.CloudCorpRecords/wattindex MCP server under?
io.github.CloudCorpRecords/wattindex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.