GeoSphere Austria Weather
PYPI · GEOSPHERE-MCP-SERVER · SCANNED SEP 21
High-resolution GeoSphere Austria weather, storms and air quality. Austria and the Alps only.
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 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 3 of 42 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1002 tokens (~250/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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
claude mcp add slettmayer-geosphere-mcp-server -- uvx geosphere-mcp-server
{
"mcpServers": {
"slettmayer-geosphere-mcp-server": {
"command": "uvx",
"args": [
"geosphere-mcp-server"
]
}
}
} {
"servers": {
"slettmayer-geosphere-mcp-server": {
"command": "uvx",
"args": [
"geosphere-mcp-server"
]
}
}
} codex mcp add slettmayer-geosphere-mcp-server -- uvx geosphere-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"slettmayer-geosphere-mcp-server": {
"type": "local",
"command": [
"uvx",
"geosphere-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add slettmayer-geosphere-mcp-server --command uvx --arg geosphere-mcp-server
mcp_servers:
slettmayer-geosphere-mcp-server:
command: "uvx"
args: ["geosphere-mcp-server"] {
"McpServers": {
"slettmayer-geosphere-mcp-server": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"geosphere-mcp-server"
]
}
}
} assistant mcp add slettmayer-geosphere-mcp-server -t stdio -c uvx -a geosphere-mcp-server
{
"mcpServers": {
"slettmayer-geosphere-mcp-server": {
"command": "uvx",
"args": [
"geosphere-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.
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 −1
- Stability: pass → 0.97 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
- Stability: 0.90 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.5.0 → 0.5.1 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −4
- Stability: pass → 0.77 functional
- 11 Sept 26 +1
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.4.3 → 0.5.0 functional
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 21 Sept 2026 · Analysed pypi/geosphere-mcp-server@0.5.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 42 packages
| Packages resolved | 42 |
|---|---|
| Stale | 2 |
| 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 →
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).
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_current_weather ~125
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. 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).
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_hourly_forecast ~202
Get an hour-by-hour weather forecast for a location. High-resolution GeoSphere AROME data (up to ~60 h, with C-LAEF precipitation probability). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| start | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_storm_outlook ~299
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. Deliberately reports no severity verdict — what counts as dangerous is the caller's judgement. High-resolution GeoSphere AROME data, whose CAPE is gated by convective inhibition. Serves Austria and the Alpine region only; a point outside that grid returns an out-of-coverage notice. The thunderstorm scan covers the AROME horizon, nominally ~60 h but shorter 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. 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).
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | – |
| longitude | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 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 848 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.