# Miso (npm · @pipeworx/mcp-miso)

Real-time electricity data for MISO, the grid operator for 15 US states from Louisiana to…

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-miso/miso-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-miso/miso-mcp)
- npm · `@pipeworx/mcp-miso`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-miso/pipeworx-mcp-miso.md), [page](https://verifymcp.io/servers/pipeworx-io-miso/pipeworx-mcp-miso)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-miso`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-miso).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-miso -- npx -y @pipeworx/mcp-miso
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-miso": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-miso"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-miso": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-miso"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-miso -- npx -y @pipeworx/mcp-miso
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-miso": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-miso"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-miso --command npx --arg -y --arg @pipeworx/mcp-miso
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-miso:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-miso"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-miso": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-miso"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-miso -t stdio -c npx -a -y @pipeworx/mcp-miso
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-miso": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-miso"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 84, +16)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-11-03 (score 68, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 83, +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.

### 2026-10-30 (score 82, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 81)

First indexed and scored.

## MCP tools (5)

### `miso_fuel_mix` (~143 tokens)

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".

Input parameters:

- `period` (string): current = the latest 5-minute interval only (default). today / yesterday = every interval of that day.

### `miso_lmp` (~193 tokens)

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.

Input parameters:

- `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.

### `miso_binding_constraints` (~117 tokens)

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".

Input parameters:

- `kind` (string): transmission = real-time transmission flowgates (default); subregional = sub-regional power-balance constraints; reserve = reserve-product constraints.

### `miso_load` (~70 tokens)

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.

### `miso_wind_solar` (~92 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-miso/pipeworx-mcp-miso#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 68
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-miso
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-miso
- Repository: https://github.com/pipeworx-io/mcp-miso
- Website: https://pipeworx.io/packs/miso
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-miso/pipeworx-mcp-miso.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-miso/pipeworx-mcp-miso.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-miso/pipeworx-mcp-miso