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.

Energi Data Dk

NPM · @PIPEWORX/MCP-ENERGI-DATA-DK · 2 COMPONENTS

Energi Data Service (Energinet) MCP — Denmark's official open energy data. Keyless. Electricity…

+18 this week 82 Trust /100

Last scanned (8 hours ago)

Scores higher than 72% 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-energi-data-dk). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 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 624 tokens (~208/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
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.

  • 5 Nov 26 +1

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

  • 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.

  • 2 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Nov 26 −14
    • Tool safety: pass → unverified ▼ security
    • Malware scan: 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
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: unverified → 0.10 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.1 → 0.2.2 functional
  • 30 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 64

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-energi-data-dk@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-energi-data-dk
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-energi-data-dk/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3635920451
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:472ed77add34bd28c65bc75980c1f8773dce313acd151bc3b62355bbcab30e9a7c86fb29a448e833ed097f6645cd5e1e61335d8eb0879eb903dbf4c42

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 · ~566 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
co2_intensity ~150

Real-time grid CO2 emission intensity (g CO2/kWh) from Energinet Denmark, sampled every 5 minutes per bidding zone (DK1=west, DK2=east); defaults to the last 12 readings (~1 hour). Lower values mean cleaner electricity.sampled every 5 minutes per bidding zone. Areas: DK1 (west Denmark), DK2 (east Denmark). Lower values mean cleaner electricity right now. Keyless official open data.

NameTypeReqDescription
areastring–Bidding zone "DK1" or "DK2". Omit for both.
limitnumber–Max records (default 12, i.e. last hour at 5-min resolution).

No output schema declared.

No examples provided.

query_dataset ~185

Generic escape hatch for any of the ~100 Energi Data Service (Energinet, Denmark) datasets. Examples: "ProductionConsumptionSettlement" (production/consumption by type per area+hour), "CO2EmisProg" (CO2 prognosis), "DayAheadPrices", "CO2Emis". Returns the raw records array for the dataset. Keyless official open data.

NameTypeReqDescription
datasetstringyesDataset name, e.g. "ProductionConsumptionSettlement".
endstring–ISO date/time upper bound.
filterobject–Column→value[] filter, e.g. {"PriceArea":["DK1"]}. Values are arrays.
limitnumber–Max records (default 20).
sortstring–Sort expression, e.g. "HourUTC DESC".
startstring–ISO date/time lower bound.

No output schema declared.

No examples provided.

spot_prices ~231

Day-ahead electricity spot prices from Energi Data Service (Energinet, Denmark/Nordic). Prices per bidding zone (PriceArea) in DKK and EUR per MWh: 15-minute intervals from 2025-10-01 (the day-ahead market moved to 15-minute products), hourly before that. Bidding zones: DK1 (west Denmark), DK2 (east Denmark), DE (Germany), NO2, SE3, SE4, and others. Omit "area" to get all zones. Keyless official open data.

NameTypeReqDescription
areastring–Bidding zone, e.g. "DK1", "DK2", "DE". Omit for all areas.
endstring–ISO date/time upper bound.
limitnumber–Max records (default 96, i.e. the last 24 hours of 15-minute rows for one area).
startstring–ISO date/time lower bound, e.g. "2026-06-01" or "2026-06-01T00:00".

No output schema declared.

No examples provided.

Install

How do I install the Energi Data Dk MCP server?

Energi Data Dk runs locally as an npm package, launched with npx -y @pipeworx/mcp-energi-data-dk. 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-energi-data-dk

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

What is the Energi Data Dk MCP server?

Energi Data Dk is an MCP server listed in the public MCP registry as io.github.pipeworx-io/energi-data-dk. Energi Data Service (Energinet) MCP, Denmark's official open energy data. Keyless. Electricity… This page covers its npm package (@pipeworx/mcp-energi-data-dk).

Is the Energi Data Dk MCP server safe to use?

Energi Data Dk 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 Energi Data Dk MCP server expose?

Energi Data Dk exposes 3 tools: spot_prices, co2_intensity, query_dataset. Their descriptions and schemas cost roughly 566 tokens of context every time the server is loaded.

Is the Energi Data Dk MCP server still maintained?

Energi Data Dk 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 Energi Data Dk MCP server under?

Energi Data Dk 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 Energi Data Dk MCP server?

VerifyMCP ran 16 checks on Energi Data Dk, 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.