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.

GeoSphere Austria Weather

PYPI · GEOSPHERE-MCP-SERVER

High-resolution GeoSphere Austria weather, storms and air quality. Austria and the Alps only.

−3 this week 87 Trust /100

Last scanned (16 hours ago)

Scores higher than 90% 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 Security99
  • No malware found by supply-chain analysis.Pass
  • 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
  • 3 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to slettmayer/geosphere-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 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 (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1215 tokens (~303/item across 4 items; 4 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 Management80
  • Stability observed for 24 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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 −3
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.80 functional
    • Package version: 0.6.0 → 0.8.0 functional
  • 4 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.7.0 → 0.8.0 functional
  • 1 Nov 26 −1
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 250 → 299 ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 0.6.0 → 0.7.0 functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 +1

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

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 pypi/geosphere-mcp-server@0.8.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 slettmayer/geosphere-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/slettmayer/geosphere-mcp-server/.github/workflows/release.yml@refs/tags/v0.8.0
Rekor log index 3640294132
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0c1a813e19acb912e3322e434fb4d5afc40f71653fd5c0e102e50bb43d2a9a07

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 41 packages
Packages resolved 41
Stale 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,047 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
get_air_quality ~222

Get air quality for a location: pollutants now and the AQI outlook. Reports current NO₂, O₃, PM10 and PM2.5 surface concentrations plus the European Air Quality Index (1-6 EEA bands) for today, tomorrow and in two days. GeoSphere's WRF-Chem forecast (3 km) serves Austria and the Alpine region only; a point outside that grid returns an out-of-coverage notice. These are model forecasts, not station measurements. An in-coverage point can still come back empty when a WRF-Chem run is stale or incomplete — the response then says so and names the source that drew the blank, which is a different answer from being out of coverage. Args: latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city names to coordinates yourself. longitude: Decimal longitude (e.g. 16.3738 for Vienna).

NameTypeReqDescription
latitudenumberyes–
longitudenumberyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_current_weather ~152

Get current weather conditions for a location. High-resolution GeoSphere Austria data (AROME/INCA/nowcast). Serves Austria and the Alpine region only; a point outside that grid returns an out-of-coverage notice. The response states which datasets served it. Observations decide whether and what is falling; the rest of the condition comes from GeoSphere's weather symbol for the current hour. Args: latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city names to coordinates yourself. longitude: Decimal longitude (e.g. 16.3738 for Vienna).

NameTypeReqDescription
latitudenumberyes–
longitudenumberyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_hourly_forecast ~259

Get an hour-by-hour weather forecast for a location. High-resolution GeoSphere AROME data (1 km, up to ~60 h). Each hour's condition is GeoSphere's own weather symbol; the precipitation chance is an estimate derived from C-LAEF ensemble percentiles (0/30/70/95 %), not a probability GeoSphere publishes. Serves Austria and the Alpine region only; a point outside that grid returns an out-of-coverage notice. Args: latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city names to coordinates yourself. longitude: Decimal longitude (e.g. 16.3738 for Vienna). hours: Number of forecast hours (default 24, clamped to 1–60). start: Optional ISO 8601 start time (e.g. "2026-07-22T15:00"); the forecast begins at/after this instant instead of now. Without an offset it is Vienna local time, like the times in the output.

NameTypeReqDescription
hoursinteger––
latitudenumberyes–
longitudenumberyes–
start–––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_storm_outlook ~414

Get the severe-weather outlook for a location: gusts and thunderstorms. Reports the peak wind gust within the next hour and the next 12 hours, whether a thunderstorm is expected within the next hour, when the next thunderstorm is expected across the whole forecast horizon, and the peak CAPE over the next 12 hours as a diagnostic. Deliberately reports no severity verdict — what counts as dangerous is the caller's judgement. An hour counts as a thunderstorm when GeoSphere's weather symbol for it is a thunderstorm, or when the C-LAEF ensemble's 90th percentiles reach 1000 J/kg CAPE and 0.1 mm precipitation (only from an ensemble run less than 12 h old). Each thunderstorm answer names its signal: symbol, ensemble or both. CAPE does not decide anything on its own. High-resolution GeoSphere AROME data (1 km) and the C-LAEF ensemble. Serves Austria and the Alpine region only; a point outside that grid returns an out-of-coverage notice. The thunderstorm scan covers the forecast horizon, nominally ~60 h but shorter after publication lag or when a run is stale or truncated. A "none in the next N h" answer names the horizon it actually covered; it is not an all-clear beyond that. "Thunderstorm expected" is unknown only when no forecast hour falls in its window. Horizons round up to whole hours: the "next hour" window covers the hour already under way plus the next one. A thunderstorm timestamp at or before the current time means one is already in progress. Args: latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city names to coordinates yourself. longitude: Decimal longitude (e.g. 16.3738 for Vienna).

NameTypeReqDescription
latitudenumberyes–
longitudenumberyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the GeoSphere Austria Weather MCP server?

GeoSphere Austria Weather runs locally as a PyPI package, launched with uvx geosphere-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · geosphere-mcp-server

# add to Claude Code
claude mcp add slettmayer-geosphere-mcp-server -- uvx geosphere-mcp-server
Common questions

What is the GeoSphere Austria Weather MCP server?

GeoSphere Austria Weather is an MCP server listed in the public MCP registry as io.github.slettmayer/geosphere-mcp-server. High-resolution GeoSphere Austria weather, storms and air quality. Austria and the Alps only. This page covers its PyPI package (geosphere-mcp-server).

Is the GeoSphere Austria Weather MCP server safe to use?

GeoSphere Austria Weather scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 GeoSphere Austria Weather MCP server expose?

GeoSphere Austria Weather exposes 4 tools: get_current_weather, get_hourly_forecast, get_storm_outlook, get_air_quality. Their descriptions and schemas cost roughly 1,047 tokens of context every time the server is loaded.

Is the GeoSphere Austria Weather MCP server still maintained?

GeoSphere Austria Weather 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 GeoSphere Austria Weather MCP server under?

GeoSphere Austria Weather 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 GeoSphere Austria Weather MCP server?

VerifyMCP ran 16 checks on GeoSphere Austria Weather, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.