Spp
NPM · @PIPEWORX/MCP-SPP · 2 COMPONENTS
Real-time electricity data for SPP, the Southwest Power Pool grid operator covering 14 US states…
Available components
Last scanned (13 hours ago)
Scores higher than 77% of npm servers
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-spp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +3
- 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. security
- Security disclosure: unverified → fail ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-spp@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-spp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-spp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692358558 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2628caeb47fb2af14a6a4e0c6cd03992bd15c173fa47aae4a1208ed650b448647d47c7aa49a8ecf8bf0aa77524b155d8d63d29c408a6ad3317b5fc997 |
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 →
spp_files ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | 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 "/". |
No output schema declared.
No examples provided.
spp_generation_mix ~187
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
spp_lmp_latest ~150
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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"). |
No output schema declared.
No examples provided.
spp_load_forecast ~141
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-spp
claude mcp add pipeworx-io-spp -- npx -y @pipeworx/mcp-spp
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.