io.github.malkreide/swiss-energy-mcp
PYPI · SWISS-ENERGY-MCP · SCANNED SEP 20
Swiss energy data via SFOE/BFE and GeoAdmin REST APIs
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 → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1451 tokens (~131/item across 11 items; 10 tools + 1 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.malkreide/swiss-energy-mcp server?
io.github.malkreide/swiss-energy-mcp runs locally as a PyPI package, launched with uvx swiss-energy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · swiss-energy-mcp
claude mcp add malkreide-swiss-energy-mcp -- uvx swiss-energy-mcp
{
"mcpServers": {
"malkreide-swiss-energy-mcp": {
"command": "uvx",
"args": [
"swiss-energy-mcp"
]
}
}
} {
"servers": {
"malkreide-swiss-energy-mcp": {
"command": "uvx",
"args": [
"swiss-energy-mcp"
]
}
}
} codex mcp add malkreide-swiss-energy-mcp -- uvx swiss-energy-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"malkreide-swiss-energy-mcp": {
"type": "local",
"command": [
"uvx",
"swiss-energy-mcp"
],
"enabled": true
}
}
} openclaw mcp add malkreide-swiss-energy-mcp --command uvx --arg swiss-energy-mcp
mcp_servers:
malkreide-swiss-energy-mcp:
command: "uvx"
args: ["swiss-energy-mcp"] {
"McpServers": {
"malkreide-swiss-energy-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"swiss-energy-mcp"
]
}
}
} assistant mcp add malkreide-swiss-energy-mcp -t stdio -c uvx -a swiss-energy-mcp
{
"mcpServers": {
"malkreide-swiss-energy-mcp": {
"command": "uvx",
"args": [
"swiss-energy-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −2
- Stability: pass → 0.83 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed pypi/swiss-energy-mcp@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| No linked repository | 1 |
| 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 →
energy_check_status ~63
Prüft die Verfügbarkeit der GeoAdmin- und opendata.swiss-APIs. <use_case>Diagnose bei unerwartetem Verhalten, Monitoring.</use_case> <important_notes>Führt zwei leichtgewichtige Test-Requests aus.</important_notes>
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| apis | array | yes | – |
| layers | array | yes | – |
| source | string | yes | – |
| summary | string | yes | – |
No examples provided.
energy_find_biogas_plants ~107
Sucht Biogasanlagen im Umkreis eines Standorts. Biogasanlagen erzeugen Energie aus organischen Abfällen und Biomasse. <use_case>Recherche zu Biomasse-Energie, regionale Kreislaufwirtschaft.</use_case> <important_notes>Quelle: ch.bfe.biogasanlagen.</important_notes> <example>lat=47.4, lon=8.5, radius_m=25000</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_find_energy_cities ~121
Sucht Gemeinden mit dem Label «Energiestadt» per Name oder Standort. <use_case>Vergleich der Energiepolitik von Gemeinden, kommunale Recherche.</use_case> <important_notes>Quelle: ch.bfe.energiestaedte. Entweder name ODER lat/lon angeben — nicht beides leer lassen.</important_notes> <example>name='Zürich' | lat=47.35, lon=8.65, radius_m=50000</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_find_hydro_plants ~113
Sucht Wasserkraftwerke (Lauf-, Speicher-, Pumpspeicher) im Umkreis eines Standorts inkl. Leistung, Fallhöhe und erwarteter Jahresproduktion. <use_case>Analyse der regionalen Wasserkraft, Infrastruktur-Recherche.</use_case> <important_notes>Quelle: ch.bfe.statistik-wasserkraftanlagen.</important_notes> <example>lat=47.05, lon=8.31, radius_m=30000</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_find_power_plants ~161
Sucht Elektrizitätsproduktionsanlagen aller Typen (Photovoltaik, Wasserkraft, Wind, Biomasse, Kernkraft) im Umkreis eines Standorts. <use_case>Standortanalysen, politische und journalistische Recherche, Schul- und Verwaltungsprojekte zur lokalen Stromproduktion.</use_case> <important_notes>Quelle: BFE-Layer ch.bfe.elektrizitaetsproduktionsanlagen. Optionaler category_filter grenzt auf einen Anlagentyp ein. Liefert max. 201 Treffer pro Aufruf.</important_notes> <example>lat=46.948, lon=7.447, radius_m=20000, category_filter='Photovoltaik'</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_find_pv_installations ~124
Sucht Photovoltaik-Grossanlagen im Umkreis eines Standorts inkl. Leistung (MWp), Jahres- und Winterproduktion sowie Projektstatus. <use_case>Recherche zu PV-Grossprojekten, Energieplanung.</use_case> <important_notes>Quelle: ch.bfe.photovoltaik-grossanlagen. Erfasst nur Grossanlagen — Einzel-PV erscheint in energy_find_power_plants.</important_notes> <example>lat=46.2, lon=7.5, radius_m=40000</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_find_wind_turbines ~138
Sucht Windenergieanlagen im Umkreis eines Standorts inkl. Betreiber, Hersteller, Modell, Nabenhöhe und Leistung. <use_case>Recherche zu Windkraft-Standorten, regionale Energieplanung.</use_case> <important_notes>Quelle: ch.bfe.windenergieanlagen. Windkraft konzentriert sich auf Jura, Wallis und Mittelland — für landesweite Suchen radius_m bis 50000 m wählen oder die Koordinaten anpassen.</important_notes> <example>lat=47.22, lon=7.05, radius_m=30000</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_location_profile ~151
Erstellt ein vollständiges Energieprofil für einen Standort und aggregiert dafür fünf BFE-Layer (Produktionsanlagen, Wind, Wasser, PV-Gross, Energiestädte) in einem einzigen Aufruf. <use_case>Schneller Gesamtüberblick für Berichte der Stadtverwaltung, Standortentscheide und Demos — beantwortet die Anchor-Frage in einem Aufruf.</use_case> <important_notes>Aggregiert mehrere parallele API-Calls; typische Laufzeit unter 5 s. Quelle: GeoAdmin / BFE.</important_notes> <example>lat=47.05, lon=8.31, radius_m=20000</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_search_bfe_datasets ~137
Durchsucht den opendata.swiss-Katalog nach Datensätzen des Bundesamts für Energie (BFE). <use_case>Auffinden von BFE-Rohdaten und Statistiken, Datenrecherche jenseits der Geo-Layer.</use_case> <important_notes>Liefert Metadaten (Titel, Beschreibung, Formate, Link) — keine Rohdaten. Volltextsuche deckt nur Metadaten ab. Paginierung über offset.</important_notes> <example>query='wasserkraft', limit=10, offset=0</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
energy_solar_potential ~155
Fragt die Solareignung von Dächern für einen Standort ab. <use_case>Entscheide über PV-Anlagen auf Schulhäusern und öffentlichen Gebäuden, Solarpotenzial-Analysen.</use_case> <important_notes>Quelle: ch.bfe.solarenergie-eignung-daecher (Rasterdaten). Kleine Radien liefern evtl. keine Treffer; der Radius wird intern auf mindestens 2000 m angehoben. Eignungsklassen: 1 (sehr gut) bis 5 (nicht geeignet).</important_notes> <example>lat=47.37, lon=8.54, radius_m=3000</example>
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results |
| license | string | yes | Licence and attribution terms |
| match_type | string | yes | 'exact', 'fuzzy' or 'none' (no results) |
| notes | – | – | Actionable hint when match_type is 'none' |
| provenance | – | yes | – |
| results | array | – | – |
| source | string | yes | Originating authority for the data |
| summary | string | yes | Human-readable Markdown summary |
No examples provided.
What is the io.github.malkreide/swiss-energy-mcp server?
io.github.malkreide/swiss-energy-mcp is listed in the public MCP registry as io.github.malkreide/swiss-energy-mcp. Swiss energy data via SFOE/BFE and GeoAdmin REST APIs. This page covers its PyPI package (swiss-energy-mcp).
Is the io.github.malkreide/swiss-energy-mcp server safe to use?
io.github.malkreide/swiss-energy-mcp scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.malkreide/swiss-energy-mcp server expose?
io.github.malkreide/swiss-energy-mcp exposes 10 tools: energy_find_power_plants, energy_find_wind_turbines, energy_find_hydro_plants, energy_find_pv_installations, energy_find_biogas_plants, and 5 more. Their descriptions and schemas cost roughly 1,270 tokens of context every time the server is loaded.
Is the io.github.malkreide/swiss-energy-mcp server still maintained?
io.github.malkreide/swiss-energy-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.malkreide/swiss-energy-mcp server under?
io.github.malkreide/swiss-energy-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.