DailyMeteo
PYPI · DAILYMETEO-MCP · 2 COMPONENTS
Historical weather and climate normals for any land location, 1 km grids, 1961 to today
Available components
Last scanned (21 hours ago)
Scores higher than 75% of PyPI servers
Category Maps and Location
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 Security100
- 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
- 1 of 37 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (GPL-2.0-or-later).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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1877 tokens (~170/item across 11 items; 11 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (18% 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 11 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
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 →
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 Nov 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.
- 19 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 −5
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.70 ▲ functional
- Package version: 0.2.2 → 0.3.0 functional
- 12 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 7 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
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 Nov 2026 · Analysed pypi/dailymeteo-mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 37 packages
| Packages resolved | 37 |
|---|---|
| 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 →
account_status DailyMeteo account and credits ~29
Plan and remaining credits: API credits (daily point and area data) and bulk credits (point history).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
app_link Open in the DailyMeteo app ~107
Link that opens the location, variable and period on the DailyMeteo map with its chart and CSV export.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | Same format; default the current year |
| lat | number | yes | Latitude in decimal degrees (WGS84) |
| lon | number | yes | Longitude in decimal degrees (WGS84) |
| start | string | – | YYYY-MM-DD, YYYY-MM or YYYY to match time_scale |
| time_scale | string | – | – |
| variable | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
download_gridded_files Download MeteoEurope1km grid archives ~205
Download MeteoEurope1km archives (1-3.5 GB per year of daily data), verify MD5, optionally unzip. Interrupted downloads resume. Tell the user the total size (list_gridded_files) before large downloads.
| Name | Type | Req | Description |
|---|---|---|---|
| dest_dir | – | – | Folder; default <output dir>/meteoeurope1km |
| period | – | – | Normal period for ltm_day / ltm_mon_ann; default both |
| product | string | – | day (one archive per year), mon (one per decade), ann (1961-2020), ltm_day / ltm_mon_ann (normals), ltm_diff (1991-2020 minus 1961-1990) |
| unzip | boolean | – | – |
| variable | string | yes | tmean, tmax, tmin, prcp or slp (sea-level pressure, daily only) |
| years | – | – | Years 1961-2020; required for day and mon |
No output schema declared.
No examples provided.
estimate_area_download Estimate area download cost ~91
Credit cost of daily rasters clipped to an area (max 3,000 km²), and the account balance.
| Name | Type | Req | Description |
|---|---|---|---|
| area_wkt | – | – | Polygon in WKT, lon lat (from find_area) |
| bbox | – | – | [west, south, east, north] |
| end | string | yes | YYYY-MM-DD |
| start | string | yes | YYYY-MM-DD |
| variables | array | yes | – |
No output schema declared.
No examples provided.
find_area Find an area (polygon) ~54
Boundary polygon (WKT) and size of a named area, for estimate_area_download / request_area_download.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Area name, e.g. 'Opština Brus' or 'Lake Bled' |
No output schema declared.
No examples provided.
find_location Find a place ~63
Latitude and longitude of a place (OpenStreetMap Nominatim). If several match, ask the user which one.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Place name, e.g. 'Kopaonik' or 'Lisbon, Portugal' |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_climate_normals Climate normals 1961-1990 vs 1991-2020 ~173
Climate normals for 1961-1990 and 1991-2020 and the change (newer minus older). Free. Without `month`, time_scale=mon returns all 12 months. Annual precipitation normals are yearly totals.
| Name | Type | Req | Description |
|---|---|---|---|
| day | – | – | Day of month, required for time_scale=day |
| lat | number | yes | Latitude in decimal degrees (WGS84) |
| lon | number | yes | Longitude in decimal degrees (WGS84) |
| month | – | – | Only this month (mon), or the month of the day (day) |
| time_scale | string | – | ann (year), mon (by month) or day (one calendar day) |
| variables | array | – | One or more of tmean, tmax, tmin (°C), prcp (mm) |
No output schema declared.
No examples provided.
get_weather Weather values for a location ~265
Daily, monthly or annual values for one location and one or more variables, 1961 to the present. Monthly and annual values are free. Daily values cost 1 credit per day and variable and need the user's DailyMeteo API key or account (see the server instructions). Results include a summary per variable; series longer than 400 rows are not listed but summarised by year and saved as CSV.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_credits | boolean | – | Set true only after the user agreed to a day request over 1000 credits |
| dates | – | – | Individual dates instead of a range, same format |
| end | – | – | Last date, same format |
| lat | number | yes | Latitude in decimal degrees (WGS84) |
| lon | number | yes | Longitude in decimal degrees (WGS84) |
| save_csv | boolean | – | Save the table as CSV (long series are always saved) |
| start | – | – | First date: YYYY-MM-DD (day), YYYY-MM (mon) or YYYY (ann); from 1961 |
| time_scale | string | – | day, mon (monthly) or ann (annual) |
| variables | array | – | One or more of tmean, tmax, tmin (°C), prcp (mm) |
No output schema declared.
No examples provided.
list_gridded_files List MeteoEurope1km grid archives ~202
MeteoEurope1km archives on Zenodo (Europe, 1 km, 1961-2020, Cloud-Optimized GeoTIFF), free. Rasters are Equi7 Europe (EPSG:27704), Int16 in tenths of the unit (°C, mm, hPa), NoData -9999.
| Name | Type | Req | Description |
|---|---|---|---|
| period | – | – | Normal period for ltm_day / ltm_mon_ann; default both |
| product | string | – | day (one archive per year), mon (one per decade), ann (1961-2020), ltm_day / ltm_mon_ann (normals), ltm_diff (1991-2020 minus 1961-1990) |
| variable | string | yes | tmean, tmax, tmin, prcp or slp (sea-level pressure, daily only) |
| years | – | – | Years 1961-2020; required for day and mon |
No output schema declared.
No examples provided.
request_area_download Order area download (email) ~112
Daily GeoTIFF rasters clipped to an area (max 3,000 km²), prepared on the server and emailed. Spends API credits: run estimate_area_download first and get the user's agreement to the cost.
| Name | Type | Req | Description |
|---|---|---|---|
| area_wkt | – | – | Polygon in WKT, lon lat (from find_area) |
| bbox | – | – | [west, south, east, north] |
| end | string | yes | YYYY-MM-DD |
| start | string | yes | YYYY-MM-DD |
| variables | array | yes | – |
No output schema declared.
No examples provided.
request_point_history Order full point history (email) ~118
Every variable, daily, for one location — by default the whole record since 1961 — as CSV by email. Costs one bulk credit (bulk credits are separate from API credits). Preparing the file takes minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | Last day YYYY-MM-DD; default the latest available day |
| lat | number | yes | Latitude in decimal degrees (WGS84) |
| lon | number | yes | Longitude in decimal degrees (WGS84) |
| start | – | – | First day YYYY-MM-DD; default the start of the record (1961) |
No output schema declared.
No examples provided.
How do I install the DailyMeteo MCP server?
DailyMeteo runs locally as a PyPI package, launched with uvx --python 3.12 dailymeteo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · dailymeteo-mcp
claude mcp add srpp011-dailymeteo-mcp -- uvx --python 3.12 dailymeteo-mcp
What is the DailyMeteo MCP server?
DailyMeteo is an MCP server listed in the public MCP registry as io.github.srpp011/dailymeteo-mcp. Historical weather and climate normals for any land location, 1 km grids, 1961 to today. This page covers its PyPI package (dailymeteo-mcp).
Is the DailyMeteo MCP server safe to use?
DailyMeteo scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 DailyMeteo MCP server expose?
DailyMeteo exposes 11 tools: find_location, find_area, get_weather, get_climate_normals, account_status, and 6 more. Their descriptions and schemas cost roughly 1,419 tokens of context every time the server is loaded.
Is the DailyMeteo MCP server still maintained?
DailyMeteo is still listed as active in the MCP registry. We last reached this channel on 21 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 DailyMeteo MCP server under?
DailyMeteo declares the GPL-2.0-or-later 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 DailyMeteo MCP server?
VerifyMCP ran 16 checks on DailyMeteo, 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.