MCP.Market

Miso MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/miso·v0.2.1

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

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Miso yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Miso tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Miso compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
250 ms
faster than 55% of 30,031 servers

Release history: 5 versions in the registry since 2026-09-25, latest 2026-11-03, typically one every 5 days.

Install Miso in Claude Code, Cursor or VS Code

claude mcp add --transport http miso https://gateway.pipeworx.io/miso/mcp
Add to Cursor

What the publisher says

From the Miso repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/miso

MISO (Midcontinent ISO) real-time electricity data — fuel mix, load, five-minute LMPs, wind/solar forecast-vs-actual and transmission binding constraints for the 15-state footprint from Louisiana to Minnesota plus Manitoba.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

wind, solar, hydro, battery storage, other) plus the footprint total. current (default) = the latest 5-minute interval; today / yesterday = the whole day.

  • misofuelmix(period?) — MW generated per fuel category (coal, gas, nuclear,

loss and congestion components and every ancillary-service clearing price (regulation, mileage, spinning, supplemental, short-term reserve, ramp up/down). ~1,600 nodes across the Central, North and South regions.

  • miso_lmp(region?, node?, limit?) — five-minute LMP $/MWh per pricing node with

shadow price. transmission (default), subregional or reserve.

  • misobindingconstraints(kind?) — the flowgates currently binding, with their

forecast for the same hours, plus the five-minute total-load series.

  • miso_load() — today's actual load hour by hour against the medium-term load
  • misowindsolar() — hourly wind and solar forecast vs actual MW.

Auth

Keyless. No registration, no key, no rate-limit documented.

Data sources

rendered as HTML at the root of that host.

  • — the live public API. Endpoint index is

page for these feeds.

  • — MISO's own

Traps

The endpoint everyone still cites is a silent zero. MISO's long-documented Real-Time Data Broker —

https://api.misoenergy.org/MISORTWDDataBroker/DataBrokerServices.asmx
  ?messageType=getfuelmix&returnType=json

— still resolves, still answers HTTP 200, and returns

{"error": "no data", "See": "https://www.misoenergy.org/markets-and-operations/rtdataapis"}

for every data messageType (getfuelmix, getlmpconsolidatedtable, gettotalload, …). Only getapiversion still carries a payload. Any client that checks res.ok reports success forever while returning nothing — the failure class in docs/silent-zero-policy.md. Verified dead 2026-09-17. This pack talks only to public-api.misoenergy.org, and misoGet throws on a body carrying a string error so a future retirement fails loudly instead of silently.

Other things worth knowing:

feed comma-grouped as "99,978". num() coerces and returns null — never 0 — for a blank, so "no reading" never reads as "zero megawatts".

  • Every number is a string. "34168", and in the /api/Snapshot display

daylight saving; the payload labels this explicitly.

  • Timestamps are EST year-round. MISO does not shift the market clock for

for the full day.

  • /api/FuelMix is one interval, not a series. Use /Today or /Yesterday

right beside it, which uses Hour. Keying both off Hour silently produces an all-null forecast column.

  • MediumTermLoadForecast uses HourEnding, not Hour — unlike ClearedMW

are absent rather than meaningful. This pack emits null for an actual whose hour has not happened, rather than reporting 0 MW of wind at 11pm.

  • /api/WindSolar/GetCombined returns future hours too, with actuals that

--compressed prints binary. Workers' fetch decompresses automatically.

  • getapiversion is gzipped without negotiation, so a raw curl without

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "miso": {
      "url": "https://gateway.pipeworx.io/miso/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Miso: common questions

Is Miso MCP server safe?
Mostly: it is graded B (77/100). Read the Miso safety report
How do I install Miso?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Miso need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Miso maintained?
The last commit was 40 days ago (2026-09-25). The latest release is v0.2.1.
Is Miso up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Miso compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 250 ms (faster than 55% of 30,031 servers). Full comparison.

More from pipeworx-io →