io.github.rfdez/pvpc-mcp-server
NPM · @RFDEZ/PVPC-MCP-SERVER · SCANNED AUG 5
Retrieve daily PVPC electricity tariffs for 2.0 TD consumers, published by Red Eléctrica.
Available components
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 →
Supply Chain Security70
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.17.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 96), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency96
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rfdez/pvpc-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 258 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability51
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 417 tokens (~417/item across 1 items; 1 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 Management30
- Stability observed for 9 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rfdez/pvpc-mcp-server
claude mcp add rfdez-pvpc-mcp-server -- npx -y @rfdez/pvpc-mcp-server
codex mcp add rfdez-pvpc-mcp-server -- npx -y @rfdez/pvpc-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rfdez-pvpc-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@rfdez/pvpc-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add rfdez-pvpc-mcp-server --command npx --arg -y --arg @rfdez/pvpc-mcp-server
mcp_servers:
rfdez-pvpc-mcp-server:
command: "npx"
args: ["-y", "@rfdez/pvpc-mcp-server"] {
"mcpServers": {
"rfdez-pvpc-mcp-server": {
"command": "npx",
"args": [
"-y",
"@rfdez/pvpc-mcp-server"
]
}
}
} 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 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Aug 26 +34
- CVE-2026-8723 affects this package: high ▼ security
- CVE-2025-15284 affects this package: high ▼ security
- CVE-2026-2391 affects this package: high ▼ security
- CVE-2026-25536 affects this package: high ▼ security
- CVE-2025-66414 affects this package: high ▼ security
- CVE-2026-0621 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- The attested source repository moved: rfdez/pvpc-mcp-server security
- MCP protocol: unverified → fail ▼ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 43
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 Aug 2026 · Analysed npm/@rfdez/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- rfdez/pvpc-mcp-server
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/rfdez/pvpc-mcp-server/.github/workflows/release.yml@refs/heads/main
- Rekor log index:
- 495582707
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:aeb7dba2359e4cf4cdf3bb847d40b25d754eb1a6fd3af8c91431525307d3f847a8c44488fb92384d9c1a58e3e91428bf64ab1b8a8db98c98a38f782af
- Discovery method:
- attestation_endpoint
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-345p-7cg4-v4c7 | CVE-2026-25536 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-8r9q-7v3j-jr4g | CVE-2026-0621 | high | yes | |
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes | |
| GHSA-6rw7-vpxm-498p | CVE-2025-15284 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-q8mj-m7cp-5q26 | CVE-2026-8723 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-w7fw-mjwx-w883 | CVE-2026-2391 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
fetch_prices Fetch PVPC Prices ~385
Fetches the Voluntary Price for the Small Consumer (PVPC) prices for a given date range and geographical area.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | — | End of the date range to filter indicator values in iso8601 format. E.g. 2025-06-29T23:59:59.999+02:00. Defaults to the end of today. |
| geographicalAggregation | string | — | How to aggregate indicator values when grouping them by geographical ID. Accepted values: `sum`, `average`. Defaults to `sum`. |
| geographicalIds | array | — | Tells the geographical IDs to filter indicator values. Accepted values: `3` (España), `8741` (Península), `8742` (Canarias), `8743` (Baleares), `8744` (Ceuta), `8745` (Melilla). Defaults to `8741`, `… |
| geographicalTruncation | string | — | Tells how to group data at geographical level when the geographical aggregation is informed. Accepted values: `country`, `electric_system`. |
| locale | string | — | Get translations for sources. Accepted values: `es`, `en`. Defaults to `es`. |
| startDate | string | — | Beginning of the date range to filter indicator values in iso8601 format. E.g. 2025-06-29T00:00:00.000+02:00. Defaults to the start of today. |
| timeAggregation | string | — | How to aggregate indicator values when grouping them by time. Accepted values: `sum`, `average`. Defaults to `sum`. |
| timeTruncation | string | — | Tells how to truncate data time series. Accepted values: `hour`, `day`, `month`, `year`. |
| Name | Type | Req | Description |
|---|---|---|---|
| prices | array | yes | — |
No examples provided.