Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.kardashev-lab/kardashev-mcp

NPM · KARDASHEV-MCP

US grid data for agents: LMP, carbon, load, queues, ERCOT large loads, RT−DA spread forecasts.

Available components

−1 this week 83 Trust /100

Last scanned (10 minutes ago)

Scores higher than 77% of npm servers

Trust breakdown (7 categories)

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 Security98
  • 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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1256 tokens (~114/item across 11 items; 11 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 Management90
  • Stability observed for 27 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
Changelog

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.

  • 5 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 27 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 25 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 19 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 18 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 16 Oct 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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/kardashev-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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,256 tokens

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 →

Tool Tokens
get_carbon ~148

Grid carbon intensity in lbs CO₂/MWh. Omit iso with latest=true for all balancing authorities; pass iso for one region. Prefer this over raw fuel-mix when the question is about emissions intensity.

NameTypeReqDescription
endstring–End date YYYY-MM-DD for history.
hoursinteger–Trailing hours of history.
isostring–ISO/BA code. Optional when latest=true (returns all).
latestboolean–If true, return latest snapshot(s). Default true when no history window.
limitinteger–Max rows (default 50, max 500).
startstring–Start date YYYY-MM-DD for history.

No output schema declared.

No examples provided.

get_curtailment ~113

Solar and wind curtailment (MWh) by ISO. Strongest coverage for CAISO, ERCOT, SPP.

NameTypeReqDescription
daysinteger–Trailing days if start/end omitted.
endstring–End date YYYY-MM-DD.
isostring–ISO code filter, e.g. CAISO or ERCOT.
limitinteger–Max rows after fetch (default 50, max 500).
startstring–Start date YYYY-MM-DD.

No output schema declared.

No examples provided.

get_forecast_track_record ~60

Public scored track record for Kardashev Labs ERCOT RT−DA spread models (MAE/RMSE/coverage/DART PnL). Use this to evaluate forecast quality; use get_spread_forecast for the live forward issuance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_fuel_mix ~157

Generation by fuel type (MW) for a US ISO. Use latest=true for the newest snapshot; otherwise returns recent history (row-capped).

NameTypeReqDescription
endstring–End date YYYY-MM-DD.
fuel_typestring–Optional fuel filter, e.g. solar, wind, gas.
isostringyesISO/RTO code, e.g. CAISO, ERCOT, MISO, NYISO, ISONE, SPP, PJM.
latestboolean–If true, return only the latest fuel-mix snapshot. Default false.
limitinteger–Max rows (default 50, max 500).
startstring–Start date YYYY-MM-DD.

No output schema declared.

No examples provided.

get_large_load ~82

ERCOT large-load interconnection queue snapshot and summary (data centers, crypto, industrial). ERCOT-only. Use summary=true for aggregates; default returns latest rows.

NameTypeReqDescription
limitinteger–Max rows when summary=false (default 50, max 500).
summaryboolean–If true, return aggregate summary instead of project rows. Default false.

No output schema declared.

No examples provided.

get_lmp ~182

Locational marginal prices (LMP) for a US ISO. market=RT (real-time) or DA (day-ahead). Optionally filter by node_id. This is settled/observed prices — for Kardashev's forward RT−DA spread forecast use get_spread_forecast instead.

NameTypeReqDescription
endstring–End date YYYY-MM-DD.
isostringyesISO/RTO code, e.g. CAISO, ERCOT, MISO, NYISO, ISONE, SPP, PJM.
limitinteger–Max rows (default 50, max 500).
marketstring–RT (real-time) or DA (day-ahead). Default RT.
node_idstring–Optional price node / hub id.
startstring–Start date YYYY-MM-DD.

No output schema declared.

No examples provided.

get_load ~120

Actual electricity demand (MW) for a US ISO or zone.

NameTypeReqDescription
endstring–End date YYYY-MM-DD.
hoursinteger–Trailing hours.
isostringyesISO/RTO code, e.g. CAISO, ERCOT, MISO, NYISO, ISONE, SPP, PJM.
limitinteger–Max rows (default 50, max 500).
startstring–Start date YYYY-MM-DD.
zonestring–Optional zone/load zone filter.

No output schema declared.

No examples provided.

get_load_forecast ~83

Near-term ISO load forecast (MW). Not the ERCOT RT−DA price-spread forecast — use get_spread_forecast for that.

NameTypeReqDescription
hoursinteger–Forecast horizon in hours. Default 24.
include_recentboolean–Include recent actuals alongside the forecast.
isostring–ISO code. Optional for default coverage.

No output schema declared.

No examples provided.

get_queue ~143

Search generator interconnection queue projects across US ISOs/RTOs — projects waiting to connect to the grid. Filter by iso, fuel_type, status, state, or min_mw.

NameTypeReqDescription
fuel_typestring–Fuel/technology filter, e.g. Solar, Wind, Storage.
isostring–ISO filter, e.g. ERCOT, MISO, PJM.
limitinteger–Max rows (default 50, max 500).
min_mwnumber–Minimum capacity MW.
statestring–US state code filter, e.g. TX.
statusstring–Queue status filter.

No output schema declared.

No examples provided.

get_spread_forecast ~113

Kardashev Labs live ERCOT day-ahead RT−DA price spread forecast (p10/p50/p90), issued before delivery and never revised. spread = RT − DA. Optional node_id filter (e.g. HB_BUSAVG, HB_NORTH). For scored historical performance use get_forecast_track_record.

NameTypeReqDescription
limitinteger–Max rows (default 50, max 500).
node_idstring–ERCOT hub/node id filter, e.g. HB_BUSAVG.

No output schema declared.

No examples provided.

list_isos ~55

List US ISOs/RTOs covered by Kardashev Labs and their live ingest status. Call this first to discover valid iso codes for other tools.

NameTypeReqDescription
include_basboolean–Include smaller balancing authorities. Default false.

No output schema declared.

No examples provided.

Install

How do I install the io.github.kardashev-lab/kardashev-mcp server?

io.github.kardashev-lab/kardashev-mcp runs locally as an npm package, launched with npx -y kardashev-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 · kardashev-mcp

# add to Claude Code
claude mcp add kardashev-lab-kardashev-mcp -- npx -y kardashev-mcp
Common questions

What is the io.github.kardashev-lab/kardashev-mcp server?

io.github.kardashev-lab/kardashev-mcp is listed in the public MCP registry as io.github.kardashev-lab/kardashev-mcp. US grid data for agents: LMP, carbon, load, queues, ERCOT large loads, RT−DA spread forecasts. This page covers its npm package (kardashev-mcp).

Is the io.github.kardashev-lab/kardashev-mcp server safe to use?

io.github.kardashev-lab/kardashev-mcp scores 83 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 io.github.kardashev-lab/kardashev-mcp server expose?

io.github.kardashev-lab/kardashev-mcp exposes 11 tools: list_isos, get_fuel_mix, get_carbon, get_lmp, get_load, and 6 more. Their descriptions and schemas cost roughly 1,256 tokens of context every time the server is loaded.

Is the io.github.kardashev-lab/kardashev-mcp server still maintained?

io.github.kardashev-lab/kardashev-mcp 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.kardashev-lab/kardashev-mcp server under?

io.github.kardashev-lab/kardashev-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.