Openei Urdb
NPM · @PIPEWORX/MCP-OPENEI-URDB · 2 COMPONENTS
OpenEI Utility Rate Database (URDB) MCP
Available components
Last scanned (4 hours ago)
Scores higher than 69% of npm servers
Category Finance and Payments
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-openei-urdb). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. 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 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
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 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 29 Oct 26 78
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-openei-urdb@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-openei-urdb |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-openei-urdb/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685085550 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:34587650b04c817457f3350f428b527cf240a9d9e51a6d261e8089f7c0c866dde6869538d69a77f865852dd43eaeaa019f5b926f078d23e168c9f82ee |
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 →
urdb_rate_detail ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Your own free NREL API key. Optional — the shared DEMO_KEY works at a low rate limit. |
| label | string | yes | URDB rate label (24-char hex id) from urdb_search_rates, e.g. "539f6b25ec4f024411ec98c9" |
No output schema declared.
No examples provided.
urdb_search_rates ~361
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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. |
No output schema declared.
No examples provided.
urdb_utilities_for_location ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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) |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-openei-urdb
claude mcp add pipeworx-io-openei-urdb -- npx -y @pipeworx/mcp-openei-urdb
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.