# Pro Flight Search Airport Delays (remote · proflightsearch.com)

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

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `proflightsearch.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-proflightsearch-airport-delays/proflightsearch.md), [page](https://verifymcp.io/servers/com-proflightsearch-airport-delays/proflightsearch)

## Channel facts

- Endpoint: `https://proflightsearch.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 575 tokens (~115/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-proflightsearch-airport-delays https://proflightsearch.com/mcp
```

### Codex

```toml
[mcp_servers.com-proflightsearch-airport-delays]
url = "https://proflightsearch.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-proflightsearch-airport-delays": {
      "type": "remote",
      "url": "https://proflightsearch.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-proflightsearch-airport-delays --url https://proflightsearch.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-proflightsearch-airport-delays:
    url: "https://proflightsearch.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-proflightsearch-airport-delays": {
      "type": "http",
      "url": "https://proflightsearch.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 74, +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.

### 2026-08-01 (score 73, +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.

### 2026-07-31 (score 72, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 72, +1)

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

### 2026-07-28 (score 71, +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.

### 2026-07-27 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 70)

First indexed and scored.

## MCP tools (4)

### `get_airport_delay_status` (~130 tokens)

Get airport delay status

Get live airport-level delay, cancellation, weather flight-rules, and 24-hour forecast context for one airport. Accepts IATA code, city, or airport name. Call this for questions like 'are there delays at JFK' or 'how is Copenhagen airport'. Airport-level only, not flight-number tracking.

Input parameters:

- `airport` (string, required): Airport IATA code, city, or airport name. Examples: JFK, LHR, Copenhagen, Chicago O'Hare.
- `format` (string): Output format. Use plain for SMS-style replies; markdown includes formatted links. Defaults to plain.

Output parameters:

- `airport` (string): Resolved airport IATA code.
- `detailsUrl` (string): Pro Flight Search airport details URL for citation or follow-up.
- `disclaimer` (string): Operational-data disclaimer for the airport status.
- `format` (string): Returned text format.
- `scope` (string): Current data scope for the tool result.
- `statusText` (string): Airport status text returned in the MCP content block.

### `airport.get_delay_status` (~118 tokens)

Get airport delay status

Get live airport-level delay, cancellation, weather flight-rules, and 24-hour forecast context for one airport. Accepts IATA code, city, or airport name. Alias of get_airport_delay_status for clients that prefer dot-notation tool names.

Input parameters:

- `airport` (string, required): Airport IATA code, city, or airport name. Examples: JFK, LHR, Copenhagen, Chicago O'Hare.
- `format` (string): Output format. Use plain for SMS-style replies; markdown includes formatted links. Defaults to plain.

Output parameters:

- `airport` (string): Resolved airport IATA code.
- `detailsUrl` (string): Pro Flight Search airport details URL for citation or follow-up.
- `disclaimer` (string): Operational-data disclaimer for the airport status.
- `format` (string): Returned text format.
- `scope` (string): Current data scope for the tool result.
- `statusText` (string): Airport status text returned in the MCP content block.

### `search_supported_airports` (~82 tokens)

Search supported airports

Search Pro Flight Search tracked airports when a user's airport reference is ambiguous. Returns matching IATA codes to use with get_airport_delay_status. Call this before airport status when the user says a city name like London or Chicago.

Input parameters:

- `query` (string, required): Airport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD.

Output parameters:

- `matches` (array): Tracked airport matches that can be used with get_airport_delay_status or airport.get_delay_status.
- `query` (string): Search query used to find tracked airports.

### `airport.search_supported` (~79 tokens)

Search supported airports

Search Pro Flight Search tracked airports when a user's airport reference is ambiguous. Returns matching IATA codes to use with airport.get_delay_status. Alias of search_supported_airports for clients that prefer dot-notation tool names.

Input parameters:

- `query` (string, required): Airport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD.

Output parameters:

- `matches` (array): Tracked airport matches that can be used with get_airport_delay_status or airport.get_delay_status.
- `query` (string): Search query used to find tracked airports.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-proflightsearch-airport-delays/proflightsearch#diagnostics

## Score history

- 2026-08-03: 74
- 2026-08-02: 73
- 2026-08-01: 73
- 2026-07-31: 72
- 2026-07-30: 70
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 70

## Links

- Remote endpoint: https://proflightsearch.com/mcp
- Repository: https://github.com/aistripes/promptair
- Website: https://proflightsearch.com/resources/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-proflightsearch-airport-delays/proflightsearch/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-proflightsearch-airport-delays/proflightsearch/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-proflightsearch-airport-delays/proflightsearch