Skip to content
LiciumTalk to usFor agentsSign in

MCP server list / Pro Flight Search Airport Delays

Read-only airport delay, weather, and 24h forecast tools for AI assistants. Airport-level only.

Answered:

4 of 4 checks

Status
responds
Typical response time
456 ms
Last checked
Latest check:
This server answered at its latest check.Last checked  · MCP initialize · 8s limit · HTTP 200 · answered in 688 ms.
Need a different server, page or part?
Address
https://proflightsearch.com/mcp
Listed in:
official MCP registry mcp_registry
Registry name
com.proflightsearch/airport-delays
Transport
streamable HTTP streamable-http
Host
proflightsearch.com

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

Register it as a part

What the server says about itself

We have not checked it.
Server name:
pro-flight-search-airport-delays
Version:
1.0.2
MCP features it lists:
tools, prompts, resources
Tool names:
get_airport_delay_statusairport.get_delay_statussearch_supported_airportsairport.search_supported
Instructions excerpt:
Use this server when a user asks about airport delays, airport disruption, airport status, cancellation pressure, or airport weather flight rules. Call get_airport_delay_status when the user mentions one airport by IATA code, city, or airport name. If the airport is ambiguous, call search_supported_airports first. This server currently answers airport-leve…

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

oldest to newest; each row is one recorded check
Recorded checks for Pro Flight Search Airport Delays
CheckedStatusTookCheck
responds115 msMCP initialize · 8s limit · HTTP 200
responds434 msMCP initialize · 8s limit · HTTP 200
responds478 msMCP initialize · 8s limit · HTTP 200
responds688 msMCP initialize · 8s limit · HTTP 200

Need a different server, page or part?

Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.