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.

UK Data: Airport weather (METAR and TAF)

REMOTE · UKDATA.RELINESS.CO.UK

Official airport weather: METAR observations and TAF forecasts from the NOAA Aviation Weather Center

+4 this week 76 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% 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 Security69
  • 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • 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
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 736 tokens (~184/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 Management47
  • Stability observed for 14 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
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 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.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ 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 21 Nov 2026 · Probed https://ukdata.reliness.co.uk/mcp/weather-observations

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=reliness.co.uk CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 f1d4f4e9f24c919b0e13c306162294a4
SANs: reliness.co.uk, ukdata.reliness.co.uk, *.ukdata.reliness.co.uk
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ukdata.reliness.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
reliness.co.uk. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ukdata.reliness.co.uk/mcp/weather-observations Verified 200
http (plaintext) http://ukdata.reliness.co.uk/mcp/weather-observations Served over HTTP 200
MCP tools · 4 exposed · ~736 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
metar_history ~197

Every METAR observation for one airport over the last N hours (up to 30 days), decoded and oldest first, plus a summary of the high and low temperature, strongest gust, flight-category low point and the weather reported. For checking what actually happened at a station: rain, gusts, fog, when it cleared. Source: NOAA/NWS Aviation Weather Center. The API returns at most 400 reports per call (about 8 days at half-hourly stations); not for flight planning. (cost: 1 credit)

NameTypeReqDescription
hoursstring–integer, optional, hours back from now, 1-720, default 24
icaostring–string, required, one ICAO station code (e.g. EGLC)
limitstring–integer, optional, most recent reports to list, 1-100, default 50 (the summary always covers the whole window)

No output schema declared.

No examples provided.

metar_latest ~166

What the weather is right now at one or more airports: the latest official METAR observation decoded into temperature (C and F), dew point, humidity, wind and gusts, visibility, cloud and ceiling, pressure and flight category. Answers "what is the temperature at Heathrow right now" with the actual station reading, not a model forecast. Source: NOAA/NWS Aviation Weather Center (worldwide airports). Only stations that reported in the last 2 hours are returned; not for flight planning. (cost: 1 credit)

NameTypeReqDescription
icaostring–string, required, ICAO station code or comma list of up to 10 (e.g. EGLC,KLGA). Use weather_station_info or metars_in_area if you do not know the code

No output schema declared.

No examples provided.

pireps_near_airport ~231

Recent pilot reports (PIREPs) within a distance of an airport: turbulence and icing with intensity, altitude, aircraft type and time, plus a tally of how many reports found none, light, moderate or severe turbulence. PIREPs are the only first-hand reports of turbulence actually encountered, so they answer "is it bumpy around Denver right now" for pilots and nervous flyers. Source: NOAA/NWS Aviation Weather Center; coverage is mainly the United States. Reports are sparse and individual; not for flight planning. (cost: 1 credit)

NameTypeReqDescription
age_hoursstring–integer, optional, how far back to look in hours, 1-24, default 3
distance_nmstring–integer, optional, radius in nautical miles, 5-500, default 100
icaostring–string, required, ICAO airport code at the centre of the search (e.g. KDEN)
limitstring–integer, optional, reports to list (newest first), 1-100, default 25

No output schema declared.

No examples provided.

taf_forecast ~142

The current Terminal Aerodrome Forecast (TAF) for an airport: the official 24-30 hour forecast for wind, visibility, weather and cloud at the airfield, decoded into time blocks with plain-English change types (temporary, becoming, 30% chance). Answers "will it be foggy or windy at the airport tomorrow morning". Source: NOAA/NWS Aviation Weather Center (worldwide airports that issue TAFs). Covers the airfield only, not the route; not for flight planning. (cost: 1 credit)

NameTypeReqDescription
icaostring–string, required, one ICAO airport code (e.g. EGLL)

No output schema declared.

No examples provided.

Install

How do I install the UK Data: Airport weather (METAR and TAF) MCP server?

UK Data: Airport weather (METAR and TAF) is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/weather-observations, 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 · ukdata.reliness.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-reliness-weather-observations 'https://ukdata.reliness.co.uk/mcp/weather-observations'
Common questions

What is the UK Data: Airport weather (METAR and TAF) MCP server?

UK Data: Airport weather (METAR and TAF) is an MCP server listed in the public MCP registry as uk.co.reliness/weather-observations. Official airport weather: METAR observations and TAF forecasts from the NOAA Aviation Weather Center. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/weather-observations).

Is the UK Data: Airport weather (METAR and TAF) MCP server safe to use?

UK Data: Airport weather (METAR and TAF) scores 76 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 UK Data: Airport weather (METAR and TAF) MCP server expose?

UK Data: Airport weather (METAR and TAF) exposes 4 tools: metar_latest, metar_history, taf_forecast, pireps_near_airport. Their descriptions and schemas cost roughly 736 tokens of context every time the server is loaded.

Does the UK Data: Airport weather (METAR and TAF) MCP server require authentication?

No. We connected to UK Data: Airport weather (METAR and TAF) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the UK Data: Airport weather (METAR and TAF) MCP server still maintained?

UK Data: Airport weather (METAR and TAF) 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 UK Data: Airport weather (METAR and TAF) MCP server?

VerifyMCP ran 13 checks on UK Data: Airport weather (METAR and TAF), 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.