Pvgis
NPM · @PIPEWORX/MCP-PVGIS · 2 COMPONENTS
PVGIS MCP — EU Joint Research Centre PV system modeler
Available components
Last scanned (12 hours ago)
Scores higher than 62% of npm servers
Category Maps and Location
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-pvgis). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 385 tokens (~128/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
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.
- 4 Nov 26 79
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-pvgis@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-pvgis |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-pvgis/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691869732 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2c96625bddcfc3bcf018458536f4f61e858de86cfeabea9d1b46024925b002fb2e267ee745984dc0f287356ee79a05af62843c195621017324e409c79 |
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 →
monthly_radiation ~110
Long-term monthly average global / diffuse / direct irradiation on horizontal / inclined plane.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | number | – | Specific tilt angle (default optimum) |
| endyear | number | – | Latest year |
| horirrad | boolean | – | Include horizontal irradiation (default true) |
| latitude | number | yes | – |
| longitude | number | yes | – |
| optrad | boolean | – | Include optimum-angle irradiation (default true) |
| startyear | number | – | Earliest year, defaults to climate database start |
No output schema declared.
No examples provided.
pv_performance ~170
Model annual + monthly PV system output. Returns kWh/year estimates and monthly breakdowns.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | number | – | Tilt angle in degrees from horizontal. Default 35. |
| aspect | number | – | Azimuth: 0=south, 90=west, -90=east, 180=north. Default 0. |
| latitude | number | yes | Latitude in degrees |
| longitude | number | yes | Longitude in degrees |
| loss | number | – | System losses (%) — default 14 |
| mountingplace | string | – | free | building (BIPV). Default free. |
| peakpower | number | – | Nominal peak power (kWp). Default 1. |
| pvtechchoice | string | – | crystSi | CIS | CdTe | Unknown. Default crystSi. |
No output schema declared.
No examples provided.
tmy ~51
Typical Meteorological Year — hourly synthetic year representative of the climate.
| Name | Type | Req | Description |
|---|---|---|---|
| endyear | number | – | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| startyear | number | – | – |
No output schema declared.
No examples provided.
How do I install the Pvgis MCP server?
Pvgis runs locally as an npm package, launched with npx -y @pipeworx/mcp-pvgis. 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-pvgis
claude mcp add pipeworx-io-pvgis -- npx -y @pipeworx/mcp-pvgis
What is the Pvgis MCP server?
Pvgis is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pvgis. PVGIS MCP, EU Joint Research Centre PV system modeler. This page covers its npm package (@pipeworx/mcp-pvgis).
Is the Pvgis MCP server safe to use?
Pvgis scores 79 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 Pvgis MCP server expose?
Pvgis exposes 3 tools: pv_performance, monthly_radiation, tmy. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.
Is the Pvgis MCP server still maintained?
Pvgis 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 Pvgis MCP server under?
Pvgis declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.