Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GridStatus (Unofficial)

NPM · @PIPEWORX/MCP-GRIDSTATUS · 2 COMPONENTS

Unofficial GridStatus MCP — wraps the GridStatus.io REST API (api.gridstatus.io/v1)

+3 this week 90 Trust /100

Last scanned (4 hours ago)

Scores higher than 85% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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-gridstatus). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 649 tokens (~216/item across 3 items; 3 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 Management80
  • Stability observed for 24 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

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 →

Changelog

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.

  • 22 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.1 → 0.2.2 functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-gridstatus@0.2.2

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-gridstatus
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-gridstatus/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3934258341
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:29c470182d43346588c3bbe9ce22d29b20dc29f7cad73f20889217ab154b5038439bbd561a048eb3ed223c0e517f8ff58095892bd20bcfa18e1cc13f9

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~597 tokens

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 →

Tool Tokens
gridstatus_datasets ~167

List/search US grid datasets (LMP prices, load, fuel mix across the 7 ISOs: CAISO, ERCOT, PJM, MISO, SPP, NYISO, ISONE). Use this to discover the exact dataset_id to pass to gridstatus_query. Example: gridstatus_datasets({ filter: "caiso lmp", _apiKey: "your-key" })

NameTypeReqDescription
_apiKeystringyesGridStatus API key (free tier at gridstatus.io)
filterstring–Optional keyword(s) to narrow the list, matched against dataset id/name/description/source (all words must match). E.g. "caiso lmp", "ercot load", "pjm fuel mix". Omit to list all.

No output schema declared.

No examples provided.

gridstatus_latest ~128

Latest values for a grid dataset — convenience that pulls the most recent rows from a recent window. Pass a dataset_id (e.g. "ercot_load", "caiso_fuel_mix"). Example: gridstatus_latest({ dataset_id: "ercot_load", _apiKey: "your-key" })

NameTypeReqDescription
_apiKeystringyesGridStatus API key
dataset_idstringyesDataset id, e.g. "ercot_load", "caiso_lmp_real_time_5_min", "pjm_fuel_mix". Discover ids via gridstatus_datasets.

No output schema declared.

No examples provided.

gridstatus_query ~302

Query a grid dataset's time-series over a time window. Pass a dataset_id from gridstatus_datasets. Common ids: caiso_lmp_real_time_5_min, ercot_load, pjm_fuel_mix. Example: gridstatus_query({ dataset_id: "caiso_lmp_real_time_5_min", start_time: "2026-07-01T00:00Z", end_time: "2026-07-01T06:00Z", limit: 100, _apiKey: "your-key" })

NameTypeReqDescription
_apiKeystringyesGridStatus API key
dataset_idstringyesDataset id to query, e.g. "caiso_lmp_real_time_5_min", "ercot_load", "pjm_fuel_mix". Discover ids via gridstatus_datasets.
end_timestring–Optional ISO end time (rows before this).
limitnumber–Max rows to return (default 50, capped at 200).
resample_frequencystring–Optional resampling bucket, e.g. "5 minutes", "1 hour", "1 day". Reduces row volume for long windows.
start_timestring–Optional ISO start time (rows on/after this). E.g. "2026-07-01T00:00Z" or "2026-07-01T00:00-05:00".

No output schema declared.

No examples provided.

Install

How do I install the GridStatus (Unofficial) MCP server?

GridStatus (Unofficial) runs locally as an npm package, launched with npx -y @pipeworx/mcp-gridstatus. 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-gridstatus

# add to Claude Code
claude mcp add pipeworx-io-gridstatus -- npx -y @pipeworx/mcp-gridstatus
Common questions

What is the GridStatus (Unofficial) MCP server?

GridStatus (Unofficial) is an MCP server listed in the public MCP registry as io.github.pipeworx-io/gridstatus. Unofficial GridStatus MCP, wraps the GridStatus.io REST API (api.gridstatus.io/v1). This page covers its npm package (@pipeworx/mcp-gridstatus).

Is the GridStatus (Unofficial) MCP server safe to use?

GridStatus (Unofficial) scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 GridStatus (Unofficial) MCP server expose?

GridStatus (Unofficial) exposes 3 tools: gridstatus_datasets, gridstatus_query, gridstatus_latest. Their descriptions and schemas cost roughly 597 tokens of context every time the server is loaded.

Is the GridStatus (Unofficial) MCP server still maintained?

GridStatus (Unofficial) is still listed as active in the MCP registry. We last reached this channel on 22 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 GridStatus (Unofficial) MCP server under?

GridStatus (Unofficial) 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 GridStatus (Unofficial) MCP server?

VerifyMCP ran 16 checks on GridStatus (Unofficial), 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.