# Pjm (npm · @pipeworx/mcp-pjm)

Real-time electricity market data from PJM Interconnection, the largest US grid operator (13…

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-pjm`
- 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-pjm).
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 875 tokens (~218/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 Pjm MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 82, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-04 (score 56, −23)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] Package version: 0.2.0 → 0.2.1

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

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `pjm_feeds` (~210 tokens)

List the feeds published by PJM Data Miner 2 — the catalog of every market-data dataset PJM exposes (LMPs, load, generation, ancillary services, capacity, transmission). Returns each feed's name and metadata so you can fetch it. Use to discover what PJM data exists before querying it. Requires a PJM API key.

Input parameters:

- `_apiKey` (string): PJM Data Miner 2 subscription key. Free after registering at https://apiportal.pjm.com/.
- `feed` (string): Optional: fetch ANY Data Miner 2 feed by its exact name (e.g. "da_hrl_lmps", "inst_load", "ops_sum_prev_period") instead of listing the catalog. This is the escape hatch for the hundreds of feeds wit…
- `row_count` (number): Rows to return (default 50, max 500).
- `start_row` (number): 1-based row offset for paging (default 1).

### `pjm_lmp_realtime` (~250 tokens)

PJM real-time five-minute locational marginal prices (LMP $/MWh) by pricing node, with the total price and its congestion and marginal-loss components. PJM is the largest US grid operator (13 states + DC, ~65M people). Use for "PJM power price right now", "PJM Western Hub price", "which PJM nodes are congested". Requires a PJM API key.

Input parameters:

- `_apiKey` (string): PJM Data Miner 2 subscription key. Free at https://apiportal.pjm.com/.
- `datetime_beginning_ept` (string): Eastern Prevailing Time range filter in Data Miner syntax, e.g. "9/17/2026 00:00 to 9/17/2026 23:59". Omit for the most recent intervals.
- `pnode_id` (string): Filter to one PJM pricing-node id (e.g. 51288 for Western Hub).
- `pnode_name` (string): Filter to one pricing-node name (e.g. "WESTERN HUB").
- `row_count` (number): Rows to return (default 50, max 500).

### `pjm_load_forecast` (~156 tokens)

PJM seven-day load forecast — forecast electricity demand in MW by forecast area (each transmission zone plus the RTO total), hour by hour. Use for "what will PJM demand be tomorrow", "PJM peak forecast this week", capacity and demand-response planning. Requires a PJM API key.

Input parameters:

- `_apiKey` (string): PJM Data Miner 2 subscription key. Free at https://apiportal.pjm.com/.
- `forecast_area` (string): Filter to one forecast area, e.g. "RTO_COMBINED", "PJM RTO", "BGE", "PEPCO".
- `row_count` (number): Rows to return (default 50, max 500).

### `pjm_generation_fuel_mix` (~207 tokens)

PJM generation by fuel type — MW generated and percentage of total from coal, natural gas, nuclear, wind, solar, hydro, oil, storage and other, per published interval. Use for "what is PJM burning right now", "PJM nuclear share", "PJM coal vs gas". Requires a PJM API key.

Input parameters:

- `_apiKey` (string): PJM Data Miner 2 subscription key. Free at https://apiportal.pjm.com/.
- `datetime_beginning_ept` (string): Eastern Prevailing Time range filter, e.g. "9/17/2026 00:00 to 9/17/2026 23:59". Omit for the most recent intervals.
- `fuel_type` (string): Filter to one fuel type, e.g. "Nuclear", "Gas", "Coal", "Wind".
- `row_count` (number): Rows to return (default 50, max 500).

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 56
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Pjm MCP server?

Pjm is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pjm. Real-time electricity market data from PJM Interconnection, the largest US grid operator (13… This page covers its npm package (@pipeworx/mcp-pjm).

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

Pjm scores 82 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 Pjm MCP server expose?

Pjm exposes 4 tools: pjm_feeds, pjm_lmp_realtime, pjm_load_forecast, pjm_generation_fuel_mix. Their descriptions and schemas cost roughly 823 tokens of context every time the server is loaded.

### Is the Pjm MCP server still maintained?

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

Pjm 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 Pjm MCP server?

VerifyMCP ran 16 checks on Pjm, 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-pjm
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-pjm
- Repository: https://github.com/pipeworx-io/mcp-pjm
- Website: https://pipeworx.io/packs/pjm
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-pjm/pipeworx-mcp-pjm.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-pjm/pipeworx-mcp-pjm/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-pjm/pipeworx-mcp-pjm.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-pjm/pipeworx-mcp-pjm