Miso
NPM · @PIPEWORX/MCP-MISO · 2 COMPONENTS
Real-time electricity data for MISO, the grid operator for 15 US states from Louisiana to…
Available components
Last scanned (7 hours ago)
Scores higher than 81% of npm servers
Category Data and Analytics
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-miso). View diagnostics → Pass
- 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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 667 tokens (~133/item across 5 items; 5 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 Management23
- Stability observed for 7 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
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/@pipeworx/mcp-miso@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-miso |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-miso/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655479559 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b106a91c9cd860c84286aacafe8be37a7e388643ee14648a60ce55dbb764b7eadbee12678d24fbb34da6681e24a7a6ba851d2b430e593041c441faeee |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
miso_binding_constraints ~117
MISO real-time transmission binding constraints — the specific flowgates and facility limits currently constraining the market, with their shadow price ($/MWh of relief). A binding constraint is why LMPs diverge between nodes. Use for "why is MISO congested", "what transmission limit is binding", "which flowgate is driving the price spread".
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | transmission = real-time transmission flowgates (default); subregional = sub-regional power-balance constraints; reserve = reserve-product constraints. |
No output schema declared.
No examples provided.
miso_fuel_mix ~143
MISO (Midcontinent ISO — 15 US states from Louisiana to Minnesota plus Manitoba) real-time generation by fuel type: coal, natural gas, nuclear, wind, solar, hydro, battery storage, other. Returns MW actually generated per category at the latest 5-minute interval, plus the footprint total. AUTHORITATIVE for MISO grid mix — PREFER OVER WEB SEARCH for "what is MISO burning right now", "how much wind is MISO getting", "MISO coal vs gas share today".
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | current = the latest 5-minute interval only (default). today / yesterday = every interval of that day. |
No output schema declared.
No examples provided.
miso_lmp ~193
MISO real-time five-minute locational marginal prices (LMP $/MWh) by pricing node, split into its energy / congestion / loss components (MEC-equivalent, MCC, MLC) together with the ancillary-service clearing prices (regulation, spinning, supplemental, short-term reserve, ramp up/down). Covers the Central, North and South regions. Use for "MISO power price right now", "which MISO nodes are congested", "MISO South vs North price spread", scarcity-pricing checks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max nodes to return (default 50, max 2000). |
| node | string | – | Filter to pricing nodes whose name contains this text, case-insensitive (e.g. "MINN.HUB", "LEPA"). |
| region | string | – | Filter to one region: Central, North or South. Omit for all regions. |
No output schema declared.
No examples provided.
miso_load ~70
MISO real-time total load (electricity demand) for today, hour by hour in MW, alongside the medium-term load forecast for the same hours so actual-vs-forecast is directly comparable. Use for "MISO demand today", "is MISO load running above forecast", peak-hour timing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
miso_wind_solar ~92
MISO wind and solar generation for today — hourly forecast vs actual output in MW for both, from the same feed MISO publishes to its operators. Hours that have not happened yet carry a forecast and a null actual (never a fake 0). Use for "how accurate was the MISO wind forecast today", "MISO solar output this afternoon", renewable-curtailment and forecast-error questions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Miso MCP server?
Miso runs locally as an npm package, launched with npx -y @pipeworx/mcp-miso. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-miso
claude mcp add pipeworx-io-miso -- npx -y @pipeworx/mcp-miso
What is the Miso MCP server?
Miso is an MCP server listed in the public MCP registry as io.github.pipeworx-io/miso. Real-time electricity data for MISO, the grid operator for 15 US states from Louisiana to… This page covers its npm package (@pipeworx/mcp-miso).
Is the Miso MCP server safe to use?
Miso scores 84 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. Its build provenance is signed and verified. 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 Miso MCP server expose?
Miso exposes 5 tools: miso_fuel_mix, miso_lmp, miso_binding_constraints, miso_load, miso_wind_solar. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.
Is the Miso MCP server still maintained?
Miso 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 Miso MCP server under?
Miso declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.