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.

Weather for Grown Ups

NPM · WEATHER-FOR-GROWN-UPS

Operational NWP, ensembles, AI weather models, regional forecasts, history, and verification.

−2 this week 87 Trust /100

Last scanned (3 hours ago)

Scores higher than 91% of npm 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 Security98
  • 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
  • 14 of 49 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 janhelcl/weather-for-grown-ups). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 56 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1607 tokens (~229/item across 7 items; 7 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 Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 14% of tool parameters carry a description.Partial
  • 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 7 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.

  • 5 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 4 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 2 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 25 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 24 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
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 npm/weather-for-grown-ups@0.5.5

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 janhelcl/weather-for-grown-ups
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/janhelcl/weather-for-grown-ups/.github/workflows/release-npm.yml@refs/tags/v0.5.5
Rekor log index 2771878539
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5043e3d6f0076c54e1a107057373c8a3634307ea2d584b1575f79f52857142e036dfbd30c7371aada1ca3e2f4252a14b00650b2589a96056b6b11afa7

Background: How many MCP packages publish verified provenance →

Dependencies 49 packages
Packages resolved 49
Stale 14
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,381 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
compare_datasets ~236

Compare only explicitly registered, scientifically compatible atmospheric dataset pairs at one point and valid time. Registered pairs: gfs↔gefs, gfs↔ifs, gefs↔ifs-ens, ifs↔ifs-ens, gfs↔aigfs, ifs↔aifs, aigfs↔aifs, gefs↔aigefs, ifs-ens↔aifs-ens, hgefs↔gefs, hgefs↔aigefs, ifs↔icon-d2, ifs↔arome, gfs↔icon-d2, ifs-ens↔icon-d2-eps, ifs-ens↔pe-arome. Pair contracts choose pressure-level or field selection explicitly. Global↔regional strategies require one shared explicit initialization cycle, sample each native grid independently at the requested coordinate, and never silently regrid or downscale. Ensemble comparisons preserve native populations and never pair member labels as trajectories. Differences, spread shifts, and raw member fractions are descriptive model evidence, not forecast error or calibrated uncertainty.

Input schema present but exposes no named parameters.

NameTypeReqDescription
datasetsarrayyes–
operationstringyes–
result–yes–

No examples provided.

compare_runs ~191

Compare forecast initialization cycles for GFS, GEFS, deterministic ECMWF IFS, or ECMWF IFS ENS through one dataset-aware contract. Deterministic GFS and IFS return newer-minus-older changes; GEFS and IFS ENS return shifts between independently summarized ensemble distributions and never treat member labels as trajectories. IFS ENS can compare 6-hourly cycles or use a 12-hour stride for long-range 00/12Z ensemble comparisons.

NameTypeReqDescription
anchorRun––Forecast initialization: latest, latest_complete where supported, or an explicit timezone-aware ISO cycle
cycleStrideHours–––
cyclesinteger––
datasetstringyes–
ensembleobject––
geometryobjectyes–
gfsGridstring––
selectionobjectyes–
thresholdGtenumber––
timeobjectyes–
NameTypeReqDescription
datasetsarrayyes–
operationstringyes–
result–yes–

No examples provided.

diagnose_atmosphere ~231

Run shared layer, profile or parcel physics through the same dataset and point/time vocabulary. Deterministic datasets evaluate the shared kernels once; ensemble datasets evaluate nonlinear diagnostics member by member before aggregation. Dataset-native cadence and capability limits remain explicit; AIGFS, AIGEFS and HGEFS do not expose parcel diagnostics because the AI constituent surface inventory lacks the required parcel initialization state, while AIFS and AIFS ENS currently expose layer/profile diagnostics but keep parcel diagnostics as an explicit capability boundary; AIGEFS, HGEFS and AIFS ENS evaluate supported diagnostics member by member before aggregation; HGEFS additionally preserves GEFS-versus-AIGEFS constituent identity.

NameTypeReqDescription
datasetstringyes–
diagnostic–yes–
ensembleobject––
forecastobject––
geometryobjectyes–
sourcestring–GFS-only source override. Omit for automatic routing: AWS S3 for point/multi-point/time-series/transect access, NOMADS for area subsets, and the resolution-matched archive for explicit old runs.
time–yes–
NameTypeReqDescription
datasetstringyes–
geometryTypestringyes–
internalDatasetIdstringyes–
kindstringyes–
result–yes–
rolestringyes–
timeTypestringyes–

No examples provided.

find_analogs ~123

Find locally materialized historical analyses similar to one target atmospheric profile. The current dataset is gfs-analysis; similarity uses the existing standardized profile metric and U/V wind representation. This is model-state similarity, not climatological rarity or impact-specific similarity.

NameTypeReqDescription
countinteger––
datasetstring––
excludeWithinHoursinteger––
fetchTargetIfMissingboolean––
geometryobjectyes–
pressureLevelsHpaarrayyes–
timeobjectyes–
variablesarrayyes–
NameTypeReqDescription
datasetsarrayyes–
operationstringyes–
result–yes–

No examples provided.

query_atmosphere ~225

Query atmospheric state through one dataset × geometry × time × selection contract across every public dataset: gfs, aigfs, aigefs, hgefs, icon-d2, icon-d2-eps, arome, pe-arome, gefs, ifs, aifs, aifs-ens, ifs-ens, gfs-analysis. Selection may be omitted for the dataset-aware default. Dataset-native domain, cadence, grid, provenance, deterministic/member-first semantics and capability limits stay explicit; unsupported combinations fail rather than being coerced into fake symmetry.

NameTypeReqDescription
aggregateobject––
datasetstringyes–
ensembleobject––
forecastobject––
geometry–yes–
limitsobject––
selectionobject––
sourcestring–GFS-only source override. Omit for automatic routing: AWS S3 for point/multi-point/time-series/transect access, NOMADS for area subsets, and the resolution-matched archive for explicit old runs.
time–yes–
NameTypeReqDescription
datasetstringyes–
geometryTypestringyes–
internalDatasetIdstringyes–
kindstringyes–
result–yes–
rolestringyes–
timeTypestringyes–

No examples provided.

search_catalog ~220

Search one canonical catalog across all atmospheric datasets. Results use shared variable, field and diagnostic IDs and explicitly list which datasets support each match. Use spatialScope and coverage to discover global or limited-area datasets that fully cover a point or bounded area; capability rows expose native grid, nominal resolution, cadence and horizon. For GEFS, forecastKind can distinguish operational capabilities from the narrower GEFSv12 reforecast subset, so retrospective queries are discoverable without pretending operational-only diagnostics exist.

NameTypeReqDescription
classificationstring––
coverage––Return only datasets whose declared spatial domain fully covers this point or bounded area.
datasetsarray––
forecastKindstring–Forecast population filter. Currently supported only with datasets=[gefs]; reforecast selects the GEFSv12 retrospective capability subset.
limitinteger––
searchstring––
sectionsarray––
spatialScopestring–Dataset spatial-domain filter. limited_area selects regional/convection-permitting datasets.
temporalSemanticsstring––
NameTypeReqDescription
datasetCapabilitiesarrayyes–
matchesarrayyes–
queryobjectyes–
totalMatchesintegeryes–
truncatedbooleanyes–

No examples provided.

verify_forecast ~155

Verify archived GFS forecasts against either later GFS analysis or IGRA v2.2 radiosondes. Atomic form uses time.at plus one leadHours value. Both references support a bounded skill-summary form using time.from/time.to plus up to three leadHours values: WFG deterministically samples at most eight nominal verification times and aggregates count, signed bias, MAE and RMSE by lead × pressure × field while retaining failed evaluations explicitly. GFS-analysis summaries are analysis-minus-forecast on the native 0.5° Grid 4 archive; IGRA summaries are observation-minus-forecast and may select an explicit or nearby station. IGRA remains a verification reference here, not a gridded query_atmosphere dataset.

Input schema present but exposes no named parameters.

NameTypeReqDescription
datasetsarrayyes–
operationstringyes–
result–yes–

No examples provided.

Install

How do I install the Weather for Grown Ups MCP server?

Weather for Grown Ups runs locally as an npm package, launched with npx -y weather-for-grown-ups. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · weather-for-grown-ups

# add to Claude Code
claude mcp add janhelcl-weather-for-grown-ups -- npx -y weather-for-grown-ups
Common questions

What is the Weather for Grown Ups MCP server?

Weather for Grown Ups is an MCP server listed in the public MCP registry as io.github.janhelcl/weather-for-grown-ups. Operational NWP, ensembles, AI weather models, regional forecasts, history, and verification. This page covers its npm package (weather-for-grown-ups).

Is the Weather for Grown Ups MCP server safe to use?

Weather for Grown Ups scores 87 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 Weather for Grown Ups MCP server expose?

Weather for Grown Ups exposes 7 tools: search_catalog, query_atmosphere, diagnose_atmosphere, compare_runs, compare_datasets, and 2 more. Their descriptions and schemas cost roughly 1,381 tokens of context every time the server is loaded.

Is the Weather for Grown Ups MCP server still maintained?

Weather for Grown Ups 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 Weather for Grown Ups MCP server under?

Weather for Grown Ups declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.