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.

io.github.malkreide/meteoswiss-mcp

PYPI · METEOSWISS-MCP

MeteoSwiss Open Data for weather, climate normals, warnings

Available components

−19 this week 74 Trust /100

Last scanned (15 hours ago)

Scores higher than 70% of PyPI servers

Category Maps and Location

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 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 build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to malkreide/meteoswiss-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 38 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2299 tokens (~255/item across 9 items; 6 tools + 3 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 Management67
  • Stability observed for 20 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 −5
    • Stability: pass → 0.60 functional
  • 1 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
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 4 Nov 2026 · Analysed pypi/meteoswiss-mcp@0.7.0

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo malkreide/meteoswiss-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/malkreide/meteoswiss-mcp/.github/workflows/publish.yml@refs/tags/v0.7.0
Rekor log index 2973998499
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:6a2483c5a282606e72a6d42a330e4986a56da81b6dfc6264d294ff1c24ddd05b

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 32 packages
Packages resolved 32
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,963 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
meteo_climate_normals ~281

<use_case> Monatliche 30-Jahres-Klimanormwerte (Temperatur ∅, Niederschlag, Sonnenstunden) für eine MeteoSwiss-Station. Referenz für «typisches Wetter» — Schuljahresplanung, Veranstaltungs-Budgetierung, Vergleich mit aktuellen Messwerten. </use_case> <important_notes> - Periode: 1991–2020 (WMO-Standard) - Eingebettete Normwerte verfügbar: KLO, SMA, BER, LUG, GVE - Für andere Stationen: Tool gibt Liste verfügbarer Codes + opendata.swiss-Link - Statische Daten — Tool ist idempotent, kein Netzwerk-Roundtrip </important_notes> <example> meteo_climate_normals(station="KLO") → Zürich/Kloten Jahresgang meteo_climate_normals(station="LUG", response_format="json") </example> Args: params (ClimateNormalsInput): - station: SMN-Kürzel (z.B. 'KLO', 'SMA', 'BER') - response_format: 'markdown' oder 'json' Returns: str: Monatliche Klimanormwerte-Tabelle 1991–2020.

NameTypeReqDescription
params–yes–
NameTypeReqDescription
resultstringyes–

No examples provided.

meteo_current ~240

<use_case> Aktuelle 10-Minuten-Wettermesswerte einer SwissMetNet-Station abrufen (Temperatur, Niederschlag, Sonnenschein, Wind, Feuchte, Druck). </use_case> <important_notes> - Granularität: 10-Minuten-Werte, letzte ~6 Beobachtungen - Quelle: BGDI STAC API (data.geo.admin.ch) - Live-Daten — Tool ist NICHT idempotent - Bei Upstream-Ausfall: Fallback mit Direktlinks statt Hard-Fail </important_notes> <example> meteo_current(station="REH") → Zürich/Affoltern (nächste SMN-Station zum Schulhaus Leutschenbach) </example> Args: params (CurrentInput): - station: SMN-Kürzel, z.B. 'KLO', 'SMA', 'REH', 'BER' - response_format: 'markdown' oder 'json' Returns: str: Aktuelle Messwerte mit Zeitstempel, oder Fallback mit Direktlinks.

NameTypeReqDescription
params–yes–
NameTypeReqDescription
resultstringyes–

No examples provided.

meteo_forecast ~394

<use_case> 1-16 Tage Wetterprognose für einen Ortsnamen oder Koordinaten — basierend auf dem MeteoSwiss-ICON-Modell (1-2 km Auflösung). Liefert Tageswerte (Temperatur Min/Max, Niederschlag, Wind, UV, Sonnenstunden, WMO-Code) und optional Stundenwerte. </use_case> <important_notes> - Modell: MeteoSwiss ICON-CH1/CH2 via Open-Meteo für Tag 1-5; darüber hinaus sowie für den UV-Index Open-Meteo best_match, weil ICON nur 5 Tage weit reicht und keinen UV-Index führt. Welcher Teil woher stammt, steht in jeder Antwort (Markdown-Fussnote bzw. JSON-Feld `modell` / `modell_details`) - location wird geokodiert (Fuzzy-Fallback bei Misserfolg); lat/lon überschreibt location und spart einen HTTP-Roundtrip - Stündliche Daten füllen die ersten 48 Stunden, nicht den vollen Range - Bei Upstream-Ausfall: Direktlinks statt Hard-Fail </important_notes> <example> meteo_forecast(location="Schulhaus Leutschenbach Zürich", days=7) meteo_forecast(latitude=47.3769, longitude=8.5417, days=3, hourly=True) </example> Args: params (ForecastInput): - location: Ortsname (geokodiert) ODER lat/lon direkt - days: Prognosetage (1–16, Standard: 7) - hourly: True für Stundenwerte - response_format: 'markdown' oder 'json' Returns: str: Tages- (und optional Stunden-)Prognose mit Wettercode und Planung.

NameTypeReqDescription
params–yes–
NameTypeReqDescription
resultstringyes–

No examples provided.

meteo_school_check ~326

<use_case> Aggregiert Geocoding + 7-Tage-Forecast + Schwellenwert-Check zu einer Ampel-Bewertung (🟢/🟡/🔴) für Schulveranstaltungen im Freien. Ein Tool-Call ersetzt die Kombi meteo_forecast + manuelle Bewertung. </use_case> <important_notes> Schwellenwerte: - Temperatur: 5–33 °C (sonst zu kalt / zu heiss) - Niederschlag: < 1.5 mm/Tag - Wind: < 50 km/h - UV-Index ≥ 6: Warnung (Sonnenschutz) Quelle: SUVA / BAG / MeteoSchweiz-Warnklassen. Bei date-Parameter: nur dieser eine Tag wird zurückgegeben. </important_notes> <example> meteo_school_check(location="Zürich Oerlikon", activity="Sporttag") meteo_school_check(location="Lugano", date="2026-06-15", activity="Schulreise") </example> Args: params (SchoolCheckInput): - location: Ort (geokodiert), z.B. 'Zürich Oerlikon' - date: Optional – spezifischer Tag (YYYY-MM-DD) - activity: Art der Aktivität ('Sporttag', 'Schulreise', etc.) Returns: str: Ampel-Bewertung für die nächsten 7 Tage (oder Einzeltag).

NameTypeReqDescription
params–yes–
NameTypeReqDescription
resultstringyes–

No examples provided.

meteo_stations ~261

<use_case> Liefert eine Übersicht der SwissMetNet (SMN)-Messstationen, die in diesem Server eingebettet sind. Nützlich, um Stationskürzel für meteo_current oder meteo_climate_normals zu finden. </use_case> <important_notes> - Kuratierte Auswahl (~20 Stationen) mit Schul-/Stadtplanungs-Fokus - Datenquelle: MeteoSwiss SMN-Katalog (160+ Stationen total) - Lizenz: CC BY 4.0 – Quelle: MeteoSchweiz </important_notes> <example> meteo_stations(canton="ZH") → KLO, SMA, REH, REC, WAE </example> Schul-Tipp: Station REH (Zürich/Affoltern) ist die nächste SMN-Station zum Schulhaus Leutschenbach. Args: params (StationsInput): - canton: Kantonskürzel (z.B. 'ZH') – leer = alle - response_format: 'markdown' oder 'json' Returns: str: Stationsliste mit Kürzel, Name, Kanton, Koordinaten und Höhe.

NameTypeReqDescription
params–yes–
NameTypeReqDescription
resultstringyes–

No examples provided.

meteo_warnings ~461

<use_case> Aktive amtliche MeteoSwiss-Wetterwarnungen (Gewitter, Sturm, Starkregen, Schnee, Hitze, Frost, Waldbrand, ...) live abrufen — landesweit, pro Kanton oder ortsgenau via PLZ. Ergänzt um Warnkarte, MeteoAlarm und OGD-Katalog. </use_case> <important_notes> - Live-Quelle ist das öffentliche MeteoSwiss-App-Backend (`app-prod-ws.meteoswiss-app.ch/v1/plzDetail`); es gibt keinen landesweiten Sammel-Endpoint, daher wird ohne `plz`/`canton` je eine Kantonshauptort-PLZ pro Kanton abgefragt und aggregiert. Für ortsgenaue Warnungen `plz` setzen. - Warnstufen-Skala: 1=Keine/gering, 2=Gering, 3=Mässig, 4=Stark, 5=Sehr stark. - Bei aktiven Warnungen Stufe 4+: Aussenveranstaltungen verschieben. - `MCP_WARNINGS_API_URL` überschreibt die App-Quelle (Vorbereitung auf die künftige offizielle OGD-Warnings-REST-API). </important_notes> <example> meteo_warnings(plz="8001") → ortsgenaue Warnungen für Zürich-City meteo_warnings(canton="TI") → Warnungen für das Tessin meteo_warnings() → landesweite Aggregation über alle Kantone </example> Args: params (WarningsInput): - canton: Kantonskürzel zum Filtern (z.B. 'ZH') - plz: 4-stellige PLZ für ortsgenaue Warnungen (z.B. '8001') - language: 'de' | 'fr' | 'it' | 'en' (Sprache der Warntexte) - response_format: 'markdown' oder 'json' Returns: str: Aktive Warnungen + Warnkarte/MeteoAlarm-Links.

NameTypeReqDescription
params–yes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the io.github.malkreide/meteoswiss-mcp server?

io.github.malkreide/meteoswiss-mcp runs locally as a PyPI package, launched with uvx meteoswiss-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 · meteoswiss-mcp

# add to Claude Code
claude mcp add malkreide-meteoswiss-mcp -- uvx meteoswiss-mcp
Common questions

What is the io.github.malkreide/meteoswiss-mcp server?

io.github.malkreide/meteoswiss-mcp is listed in the public MCP registry as io.github.malkreide/meteoswiss-mcp. MeteoSwiss Open Data for weather, climate normals, warnings. This page covers its PyPI package (meteoswiss-mcp).

Is the io.github.malkreide/meteoswiss-mcp server safe to use?

io.github.malkreide/meteoswiss-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 io.github.malkreide/meteoswiss-mcp server expose?

io.github.malkreide/meteoswiss-mcp exposes 6 tools: meteo_stations, meteo_current, meteo_forecast, meteo_school_check, meteo_climate_normals, meteo_warnings. Their descriptions and schemas cost roughly 1,963 tokens of context every time the server is loaded.

Is the io.github.malkreide/meteoswiss-mcp server still maintained?

io.github.malkreide/meteoswiss-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.malkreide/meteoswiss-mcp server under?

io.github.malkreide/meteoswiss-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.