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.

DailyMeteo

REMOTE · MCP.GILAB.RS · 2 COMPONENTS

Historical weather and climate normals for any land location, 1 km grids, 1961 to today

69 Trust /100

Last scanned (22 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1337 tokens (~222/item across 6 items; 6 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
  • Structured output schemas are declared (33% 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 7 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 (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 20 Nov 26 +1

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

  • 19 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 18 Nov 26 68

    First indexed and scored.

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 21 Nov 2026 · Probed https://mcp.gilab.rs/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.gilab.rs CN=YR1,O=Let's Encrypt,C=US 18 Nov 2026 16 Feb 2027 RSA 2048 SHA256-RSA 6c9ccef4a544afed4dff6c96bd750e220a1
SANs: mcp.gilab.rs
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.gilab.rs. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
rs. DS published 57382 13 Verified
gilab.rs. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.gilab.rs/mcp Verified 200
http (plaintext) http://mcp.gilab.rs/mcp HTTPS enforced 301 https://mcp.gilab.rs/mcp
MCP tools · 6 exposed · ~871 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
app_link ~107

Link that opens the location, variable and period on the DailyMeteo map with its chart and CSV export.

NameTypeReqDescription
end––Same format; default the current year
latnumberyesLatitude in decimal degrees (WGS84)
lonnumberyesLongitude in decimal degrees (WGS84)
startstring–YYYY-MM-DD, YYYY-MM or YYYY to match time_scale
time_scalestring––
variablestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

find_area ~54

Boundary polygon (WKT) and size of a named area, for estimate_area_download / request_area_download.

NameTypeReqDescription
querystringyesArea name, e.g. 'Opština Brus' or 'Lake Bled'

No output schema declared.

No examples provided.

find_location ~63

Latitude and longitude of a place (OpenStreetMap Nominatim). If several match, ask the user which one.

NameTypeReqDescription
limitinteger––
querystringyesPlace name, e.g. 'Kopaonik' or 'Lisbon, Portugal'
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_climate_normals ~175

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.

NameTypeReqDescription
day––Day of month, required for time_scale=day
latnumberyesLatitude in decimal degrees (WGS84)
lonnumberyesLongitude in decimal degrees (WGS84)
month––Only this month (mon), or the month of the day (day)
time_scalestring–ann (year), mon (by month) or day (one calendar day)
variablesarray–One or more of tmean, tmax, tmin (°C), prcp (mm)

No output schema declared.

No examples provided.

get_weather ~268

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.

NameTypeReqDescription
confirm_creditsboolean–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
latnumberyesLatitude in decimal degrees (WGS84)
lonnumberyesLongitude in decimal degrees (WGS84)
save_csvboolean–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_scalestring–day, mon (monthly) or ann (annual)
variablesarray–One or more of tmean, tmax, tmin (°C), prcp (mm)

No output schema declared.

No examples provided.

list_gridded_files ~204

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.

NameTypeReqDescription
period––Normal period for ltm_day / ltm_mon_ann; default both
productstring–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)
variablestringyestmean, 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.

Install

How do I install the DailyMeteo MCP server?

DailyMeteo is a hosted endpoint at https://mcp.gilab.rs/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.gilab.rs

# add to Claude Code
claude mcp add --transport http srpp011-dailymeteo-mcp 'https://mcp.gilab.rs/mcp'
Common questions

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 hosted endpoint (https://mcp.gilab.rs/mcp).

Is the DailyMeteo MCP server safe to use?

DailyMeteo scores 69 out of 100 on VerifyMCP. 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 6 tools: find_location, find_area, get_weather, get_climate_normals, app_link, list_gridded_files. Their descriptions and schemas cost roughly 871 tokens of context every time the server is loaded.

Does the DailyMeteo MCP server require authentication?

No. We connected to DailyMeteo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the DailyMeteo MCP server?

VerifyMCP ran 13 checks on DailyMeteo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.