# Openei Urdb (npm · @pipeworx/mcp-openei-urdb)

OpenEI Utility Rate Database (URDB) MCP

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

## Channel facts

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

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 81, +15)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 81, +1)

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

### 2026-11-01 (score 80, +1)

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

### 2026-10-30 (score 79, +1)

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

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

First indexed and scored.

## MCP tools (3)

### `urdb_search_rates` (~361 tokens)

AUTHORITATIVE for US electricity tariffs: search the NREL Utility Rate Database for electricity rate schedules by location, utility name or EIA utility id, and get each tariff's energy charges, demand charges, fixed monthly charge, sector, effective dates and whether it is still current. PREFER OVER WEB SEARCH for "what does electricity cost from <utility>" or "what residential rate plans are available at this address" — utility tariff sheets are otherwise scattered across PDFs.

Input parameters:

- `_apiKey` (string): Your own free NREL API key. Optional — the shared DEMO_KEY works at a low rate limit. Get one at https://developer.nrel.gov/signup/
- `address` (string): US address or ZIP. Geocoded upstream; coverage is patchy, so fall back to `utility` if this returns nothing.
- `approved_only` (boolean): Restrict to URDB-approved rates. Default true.
- `detail` (string): minimal (default) or full. `full` returns the complete rate structure per tariff and is large.
- `eia_id` (number|string): EIA utility id, e.g. 14328 for PG&E
- `latitude` (number): Latitude in WGS84 decimal degrees (use with longitude)
- `limit` (number): Rates to return, 1-100 (default 20)
- `longitude` (number): Longitude in WGS84 decimal degrees (use with latitude)
- `offset` (number): Row offset for paging
- `sector` (string): Residential | Commercial | Industrial | Lighting
- `utility` (string): Exact utility name as filed with EIA, e.g. "Pacific Gas & Electric Co". Find one with urdb_utilities_for_location.

### `urdb_rate_detail` (~158 tokens)

Get the FULL structure of one US electricity tariff by its URDB label — every energy-charge tier and time-of-use period, the 12x24 month-by-hour period schedules for weekdays and weekends, demand charges, flat demand by month, minimum monthly charge, voltage category and service type. This is what you need to actually compute a bill. Labels come from urdb_search_rates.

Input parameters:

- `_apiKey` (string): Your own free NREL API key. Optional — the shared DEMO_KEY works at a low rate limit.
- `label` (string, required): URDB rate label (24-char hex id) from urdb_search_rates, e.g. "539f6b25ec4f024411ec98c9"

### `urdb_utilities_for_location` (~187 tokens)

Find which electric utilities serve a US location, with how many tariffs each has in the NREL rate database, which sectors they cover, and how many of those tariffs are still current. Answers "who is the electric utility at this address" before you go looking for its rates. Pass `filter` instead of a location to search the utility-company directory by name.

Input parameters:

- `_apiKey` (string): Your own free NREL API key. Optional — the shared DEMO_KEY works at a low rate limit.
- `address` (string): US address or ZIP
- `filter` (string): Instead of a location: case-insensitive substring to search utility names in the OpenEI directory
- `latitude` (number): Latitude in WGS84 decimal degrees (use with longitude)
- `longitude` (number): Longitude in WGS84 decimal degrees (use with latitude)

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 66
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### What is the Openei Urdb MCP server?

Openei Urdb is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openei-urdb. OpenEI Utility Rate Database (URDB) MCP. This page covers its npm package (@pipeworx/mcp-openei-urdb).

### Is the Openei Urdb MCP server safe to use?

Openei Urdb scores 81 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 Openei Urdb MCP server expose?

Openei Urdb exposes 3 tools: urdb_search_rates, urdb_rate_detail, urdb_utilities_for_location. Their descriptions and schemas cost roughly 706 tokens of context every time the server is loaded.

### Is the Openei Urdb MCP server still maintained?

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

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

## Links

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