@pipeworx/iso-ne
Connect: https://gateway.pipeworx.io/iso-ne/mcp · Install: one-click buttons
No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.
Tools: 3
ISO New England market data via ISO Express web services — five-minute LMPs, system load and generation fuel mix for the six New England states (CT, MA, ME, NH, RI, VT).
Tools
isone_lmp(location_id?, date?, limit?)— five-minute real-time LMP with energy, congestion and loss components. Omitdatefor the current interval.isone_load(date?, limit?)— five-minute total system load in MW.isone_fuel_mix(date?, limit?)— generation by fuel category (gas, nuclear, hydro, wind, solar, refuse, wood, coal, oil, landfill gas, imports) with the marginal-fuel flag.
Auth
BYO only today. HTTP Basic against webservices.iso-ne.com.
Platform fallback env var — not provisioned: PLATFORM_ISONE_AUTH.
Registration is free at https://www.iso-ne.com/participate/applications-status-changes/ (an “ISO Express / Web Services” account), but ISO-NE approves the account before the credentials work. A brand-new registration is refused exactly like a wrong password, so the pack’s 401 message names the approval step rather than implying the password is wrong.
_apiKey accepts either spelling:
"username:password"— plain; the pack base64-encodes it.base64("username:password")— pre-encoded, same convention asseo-serp.
Anything else fails locally with a clear message instead of becoming a bare upstream 401 that looks like an outage.
One env var, not PLATFORM_ISONE_USER + PLATFORM_ISONE_PASS: the gateway
injects exactly one secret per pack, into _apiKey. So the stored credential is
the single string the Basic scheme actually needs. The pack is marked
byoExpected: true in workers/gateway/src/pack-manifest.json so the vendor-key
ratchet does not fail the deploy; drop it the day the credential lands.
Data sources
- https://webservices.iso-ne.com/api/v1.1/ — the authenticated API.
/fiveminutelmp/current,/fiveminutesystemload/current,/genfuelmix/current, and/…/day/YYYYMMDDfor a historical day. - https://www.iso-ne.com/isoexpress/ — the public browser UI over the same data.
Traps
- There is no keyless fallback. This was checked, not assumed. Probed
2026-09-17, all refused:
webservices.iso-ne.com/api/v1.1/fiveminutesystemload/current→ 401www.iso-ne.com/ws/wsclient→ 500 (for every parameter shape tried)www.iso-ne.com/transform/csv/genfuelmix?start=…→ 403, and it stays 403 with a browser User-Agent and an isoexpressReferer. Note it is a 403 and not a 404, so the path exists — it is session-gated, not merely UA-gated (cf.reference_gov_site_ua_blocks, where a UA swap is usually the fix).
- Response shapes here are UNVERIFIED. Holding no account, no ISO-NE response
body in this pack has been observed live. ISO-NE wraps results in a
singular/plural pair —
{"FiveMinLmps": {"FiveMinLmp": [...]}}— and the pack unwraps that generically (descend to the first array-valued property) and returns rows as published, without remapping field names. Theenvelopefield in every response reports which keys it actually walked, so the first real call with a credential tells you the true shape rather than hiding it. Tighten once credentials exist. - Same-day requests can legitimately be empty. ISO-NE publishes each day’s reports after the fact. The pack treats a 0-row success as an error and says to try the previous day, rather than returning an empty array as a clean answer.
- ISO-NE does not use a
.jsonsuffix consistently across its docs; this pack appends.jsonto every path, which is the form the v1.1 API accepts.
Tools
- isone_lmp — ISO New England five-minute real-time locational marginal prices (LMP $/MWh) with their energy, congestion and loss components, for the eight New England load zones and hubs. ISO-NE runs the grid and
- isone_load — ISO New England system load (total electricity demand) in MW at five-minute resolution for the six-state New England footprint. Use for “New England electricity demand right now”, “ISO-NE peak load to
- isone_fuel_mix — ISO New England generation by fuel category in MW — natural gas, nuclear, hydro, wind, solar, refuse, wood, coal, oil, landfill gas and net interchange with neighbouring grids — with the marginal-fuel
Tools
isone_fuel_mix— ISO New England generation by fuel category in MW — natural gas, nuclear, hydro, wind, solar, refuse, wood, coal, oil, landfill gas and net interchange with neighbouring grids — with the marginal-fuelisone_lmp— ISO New England five-minute real-time locational marginal prices (LMP $/MWh) with their energy, congestion and loss components, for the eight New England load zones and hubs. ISO-NE runs the grid andisone_load— ISO New England system load (total electricity demand) in MW at five-minute resolution for the six-state New England footprint. Use for New England electricity demand right now , ISO-NE peak load toda