UAV Forecast
REMOTE · MCP.UAVFORECAST.COM
Drone flying conditions checked against your own UAV Forecast settings: verdicts, wind, Kp.
Available components
Last scanned (14 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1401 tokens (~280/item across 5 items; 5 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 (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 →
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.
- 19 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.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 78
First indexed and scored.
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.uavforecast.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.uavforecast.com | CN=YE1,O=Let's Encrypt,C=US | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 55a5c24990ee61484d662bafe74a001b18f |
| SANs: mcp.uavforecast.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.uavforecast.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| uavforecast.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.uavforecast.com/.well-known/oauth-protected-resource/mcp", scope="forecast"
Bearer resource_metadata="https://mcp.uavforecast.com/.well-known/oauth-protected-resource/mcp", scope="forecast" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors https://dakboard.com; |
| x-frame-options | SAMEORIGIN |
Protected resource metadata
| Document | https://mcp.uavforecast.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.uavforecast.com/mcp |
| Authorisation server | https://mcp.uavforecast.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.uavforecast.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.uavforecast.com/mcp | HTTPS enforced | 301 | https://mcp.uavforecast.com/mcp |
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 →
check_good_to_fly Check good to fly ~383
Answers: can I fly my drone now, when today or this week, where (compare up to 5 places), which day is best, and why not. Judges every hour against the user's own thresholds, flying hours and profile, and returns good windows, the runs of hours that fail and why, per-day summaries for longer ranges, and weather warnings in effect. "Good" means within the user's own UAV Forecast limits, not safe; airspace, permissions, aircraft limits and battery are not included. Current factor keys: wind_at_altitude, max_altitude, temp_or_wind_chill, humidity, delta_t, precip_prob, precip_intensity, thunder_prob, cloud_cover, cloud_base, icing, visibility, sun_elevation, gps, kp, gps_kp, gust_at_altitude; unknown keys may appear. Current notice kinds: weather_alert; more kinds may appear. Anything the plan, region or data sources don't include is listed under "unavailable" with a reason (plan, region, source, setting).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | From now to local midnight after this many days (1 = the rest of today). Not with start/end or hours. |
| end | string | – | Local date or date-time; exclusive for a date-time, inclusive for a date. |
| hours | integer | – | From now for this many hours. Not with start/end or days. |
| locale | string | – | BCP 47 language tag for labels. |
| places | array | yes | Favorite location names, place names, coordinates, or "here". |
| profile | string | – | A saved settings profile's name, to answer with that profile's settings instead of the current ones. |
| start | string | – | Local date (YYYY-MM-DD) or date-time (YYYY-MM-DDTHH:MM) at the place. |
| Name | Type | Req | Description |
|---|---|---|---|
| coarsened | boolean | – | – |
| link | string | – | – |
| message | string | – | – |
| note | string | – | – |
| places | array | – | – |
| source | string | – | Source: UAV Forecast |
| status | string | yes | ok or subscription_required; others may appear. |
| unavailable | array | – | – |
| units | – | – | – |
No examples provided.
get_hourly_forecast Hourly forecast ~412
Answers: what will the wind, gusts, temperature, rain, cloud and other conditions be at a place and time, including wind and gusts at chosen heights above ground, and what were they in past hours the plan includes. Returns hourly values in the user's units, each with its status against the user's thresholds. "Good" means within the user's own UAV Forecast limits, not safe; airspace, permissions, aircraft limits and battery are not included. Current factor keys: wind_at_altitude, max_altitude, temp_or_wind_chill, humidity, delta_t, precip_prob, precip_intensity, thunder_prob, cloud_cover, cloud_base, icing, visibility, sun_elevation, gps, kp, gps_kp, gust_at_altitude; unknown keys may appear. Anything the plan, region or data sources don't include is listed under "unavailable" with a reason (plan, region, source, setting).
| Name | Type | Req | Description |
|---|---|---|---|
| altitude_units | string | – | m or ft; set it whenever the user names a unit. |
| altitudes | array | – | Heights above ground (AGL) in altitude_units; without altitude_units, the user's altitude units (see get_my_settings). Each must be above 0: the lowest forecast wind is the surface wind at 10 m (33 f… |
| factors | array | – | The factors to read; without it, those with an enabled threshold plus wind and gust. |
| hours | integer | – | How many hours from start. |
| locale | string | – | BCP 47 language tag for labels. |
| place | string | yes | A favorite location's name, a place name, "lat, lon" coordinates, or "here". |
| profile | string | – | A saved settings profile's name, to answer with that profile's settings instead of the current ones. |
| start | string | – | Local date or date-time; may be in the past within your plan's historical window. |
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | – | – |
| historical | boolean | – | – |
| hours | array | – | – |
| link | string | – | – |
| message | string | – | – |
| note | string | – | – |
| now_local | – | – | – |
| place | – | – | – |
| range | – | – | – |
| source | string | – | Source: UAV Forecast |
| status | string | yes | ok or subscription_required; others may appear. |
| timezone | string | – | – |
| unavailable | array | – | – |
| units | – | – | – |
No examples provided.
get_my_settings My UAV Forecast settings ~134
Answers: what are my limits and units, what does my plan include, which profiles and favorite locations do I have, and why did a verdict come out as it did. Favorite locations are listed by name only. Current factor keys: wind_at_altitude, max_altitude, temp_or_wind_chill, humidity, delta_t, precip_prob, precip_intensity, thunder_prob, cloud_cover, cloud_base, icing, visibility, sun_elevation, gps, kp, gps_kp, gust_at_altitude; unknown keys may appear.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | BCP 47 language tag for labels. |
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | – | – |
| flying_hours | – | – | – |
| link | string | – | – |
| message | string | – | – |
| note | string | – | – |
| plan_includes | object | – | – |
| profiles | array | – | – |
| saved_locations | array | – | – |
| source | string | – | Source: UAV Forecast |
| status | string | yes | ok or subscription_required; others may appear. |
| thresholds | array | – | – |
| unavailable | array | – | – |
| units | – | – | – |
No examples provided.
get_space_weather Space weather and Kp ~140
Answers: what is the Kp index now and over the next 3 days, is a geomagnetic storm expected, and will GPS be affected by the user's Kp threshold. Uses the Kp source the user's app uses, and labels every value with its source. Anything the plan, region or data sources don't include is listed under "unavailable" with a reason (plan, region, source, setting).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | BCP 47 language tag for labels. |
| place | string | – | A favorite location's name, a place name, "lat, lon" coordinates, or "here". Times are then local there. |
| Name | Type | Req | Description |
|---|---|---|---|
| forecast | array | – | – |
| gps | object | – | – |
| kp_now | object | – | – |
| kp_source | string | – | uavforecast or noaa. |
| link | string | – | – |
| message | string | – | – |
| noaa_forecast | – | – | – |
| note | string | – | – |
| source | string | – | Source: UAV Forecast |
| status | string | yes | ok or subscription_required; others may appear. |
| storm_watch | array | – | – |
| timezone | string | – | – |
| unavailable | array | – | – |
No examples provided.
search_places Search places ~85
Answers: which place is meant when a name is ambiguous, such as several towns with the same name. The user's favorite locations whose names match come first. Optionally ranks the other results near another place or "here".
| Name | Type | Req | Description |
|---|---|---|---|
| near | string | – | A place name or "here" to rank results near. |
| query | string | yes | A place name, or part of one. |
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | – | – |
| message | string | – | – |
| note | string | – | – |
| results | array | – | – |
| source | string | – | Source: UAV Forecast |
| status | string | yes | ok or subscription_required; others may appear. |
| unavailable | array | – | – |
No examples provided.
How do I install the UAV Forecast MCP server?
UAV Forecast is a hosted endpoint at https://mcp.uavforecast.com/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.uavforecast.com
claude mcp add --transport http com-uavforecast-uav-forecast 'https://mcp.uavforecast.com/mcp'
What is the UAV Forecast MCP server?
UAV Forecast is an MCP server listed in the public MCP registry as com.uavforecast/uav-forecast. Drone flying conditions checked against your own UAV Forecast settings: verdicts, wind, Kp. This page covers its hosted endpoint (https://mcp.uavforecast.com/mcp).
Is the UAV Forecast MCP server safe to use?
UAV Forecast scores 79 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 UAV Forecast MCP server expose?
UAV Forecast exposes 5 tools: check_good_to_fly, get_hourly_forecast, get_space_weather, get_my_settings, search_places. Their descriptions and schemas cost roughly 1,154 tokens of context every time the server is loaded.
Does the UAV Forecast MCP server require authentication?
Yes. UAV Forecast asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the UAV Forecast MCP server still maintained?
UAV Forecast 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 UAV Forecast MCP server?
VerifyMCP ran 13 checks on UAV Forecast, 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.