Remote MCP · Endpoint

UK Data: Airport weather (METAR and TAF) MCP server

No. UK Data: Airport weather (METAR and TAF) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ukdata.reliness.co.uk/mcp/weather-observations

The last check completed an MCP handshake.

Registry name
uk.co.reliness/weather-observations
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
4 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Official airport weather: METAR observations and TAF forecasts from the NOAA Aviation Weather Center
Listing
From the official MCP registry (active).
Recent checks of UK Data: Airport weather (METAR and TAF)
CheckedResultHandshake
1 hour agoHandshake completed73 ms
4 days agoHandshake completed53 ms
7 days agoFailed - the check failed for an unclassified reason—

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 3.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with UK Data: Airport weather (METAR and TAF) and makes no claim about it beyond what these checks measured.