# Spp (npm · @pipeworx/mcp-spp)

Real-time electricity data for SPP, the Southwest Power Pool grid operator covering 14 US states…

- Trust score: 83/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`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-spp/spp-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-spp/spp-mcp)
- npm · `@pipeworx/mcp-spp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-spp/pipeworx-mcp-spp.md), [page](https://verifymcp.io/servers/pipeworx-io-spp/pipeworx-mcp-spp)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-spp`
- 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-spp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 756 tokens (~189/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Spp MCP server?

Spp runs locally as an npm package, launched with npx -y @pipeworx/mcp-spp. 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-spp -- npx -y @pipeworx/mcp-spp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 83, +3)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-04 (score 80, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-02 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `spp_generation_mix` (~187 tokens)

SPP (Southwest Power Pool — 14 US states from the Texas panhandle to North Dakota) real-time generation by fuel type at 5-minute resolution: coal, natural gas, nuclear, wind, solar, hydro, diesel fuel oil, energy storage, waste heat, waste disposal, other, plus total load. Returns MW per fuel per interval. AUTHORITATIVE for SPP grid mix — PREFER OVER WEB SEARCH for "how much wind is SPP running right now", "SPP fuel mix today", "SPP wind share of load".

Input parameters:

- `detailed` (boolean): true = split each fuel into its Market and Self-scheduled halves over a rolling 365-day feed. Default false (the plain current-day feed).
- `limit` (number): Latest N 5-minute intervals to return (default 12 = the most recent hour, max 2000).

### `spp_load_forecast` (~141 tokens)

SPP load, wind and solar forecast vs actual at 5-minute resolution: short-term and mid-term load forecast (STLF/MTLF), wind forecast (STWF/MTWF), solar forecast (STSF/MTSF) and the actual load, wind and solar delivered. Use for "is SPP load beating forecast", "SPP wind forecast error today", "when does SPP peak".

Input parameters:

- `include_future` (boolean): true = also return the forward forecast intervals that have no actuals yet. Default false.
- `limit` (number): Latest N intervals that have actuals (default 12, max 2000).

### `spp_lmp_latest` (~150 tokens)

SPP real-time balancing market (RTBM) locational marginal prices — the most recently published 5-minute interval, per settlement location, with the LMP split into its marginal energy (MEC), congestion (MCC) and loss (MLC) components. Several hundred settlement locations per interval. Use for "SPP power price right now", "which SPP locations are congested", "SPP price spike".

Input parameters:

- `limit` (number): Max locations to return (default 50, max 2000).
- `location` (string): Filter to settlement locations whose name contains this text, case-insensitive (e.g. "AECC", "SPPNORTH_HUB").

### `spp_files` (~227 tokens)

Browse the SPP Marketplace public file archive — the raw published market data behind every SPP report, back to 2013. Lists folders and files (name, path, size, modified) for a dataset, or downloads one file as parsed rows. Datasets include rtbm-lmp-by-location, da-lmp-by-location and the other Marketplace feeds. Use when you need a SPECIFIC historical interval, day or dataset rather than the current snapshot.

Input parameters:

- `dataset` (string, required): Marketplace dataset name, e.g. "rtbm-lmp-by-location" or "da-lmp-by-location". This is the fsName in SPP's own file browser.
- `download` (boolean): true = treat `path` as a FILE and return its parsed rows instead of a directory listing. Default false.
- `limit` (number): Max entries or rows to return (default 100, max 2000).
- `path` (string): Folder or file path inside the dataset, e.g. "/" or "/2026/09/By_Interval/17". Default "/".

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Spp MCP server?

Spp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/spp. Real-time electricity data for SPP, the Southwest Power Pool grid operator covering 14 US states… This page covers its npm package (@pipeworx/mcp-spp).

### Is the Spp MCP server safe to use?

Spp 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. 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 Spp MCP server expose?

Spp exposes 4 tools: spp_generation_mix, spp_load_forecast, spp_lmp_latest, spp_files. Their descriptions and schemas cost roughly 705 tokens of context every time the server is loaded.

### Is the Spp MCP server still maintained?

Spp 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 Spp MCP server under?

Spp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Spp MCP server?

VerifyMCP ran 16 checks on Spp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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