Pro Flight Search Airport Delays
REMOTE · PROFLIGHTSEARCH.COM · SCANNED AUG 3
Read-only airport delay, weather, and 24h forecast tools for AI assistants. Airport-level only.
Available components
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 →
Endpoint Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 575 tokens (~115/item across 5 items; 4 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · proflightsearch.com
claude mcp add --transport http com-proflightsearch-airport-delays https://proflightsearch.com/mcp
[mcp_servers.com-proflightsearch-airport-delays] url = "https://proflightsearch.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-proflightsearch-airport-delays": {
"type": "remote",
"url": "https://proflightsearch.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-proflightsearch-airport-delays --url https://proflightsearch.com/mcp --transport streamable-http
mcp_servers:
com-proflightsearch-airport-delays:
url: "https://proflightsearch.com/mcp" {
"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.
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.
- 3 Aug 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.
- 1 Aug 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.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 70
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 3 Aug 2026 · Probed https://proflightsearch.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proflightsearch.com | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | d8bbdb0d97df556b0ee4203d59bdf2bb |
| SANs: proflightsearch.com, www.proflightsearch.com, *.www.proflightsearch.com | ||||||
| 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 |
DNSSEC insecure
Validation of proflightsearch.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| proflightsearch.com. | absent | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://proflightsearch.com/mcp | Verified | 200 | |
| http (plaintext) | http://proflightsearch.com/mcp | HTTPS enforced | 301 | https://proflightsearch.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.
airport.get_delay_status Get airport delay status ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | Resolved airport IATA code. |
| detailsUrl | string | yes | Pro Flight Search airport details URL for citation or follow-up. |
| disclaimer | string | yes | Operational-data disclaimer for the airport status. |
| format | string | yes | Returned text format. |
| scope | string | yes | Current data scope for the tool result. |
| statusText | string | yes | Airport status text returned in the MCP content block. |
No examples provided.
airport.search_supported Search supported airports ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Airport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | Tracked airport matches that can be used with get_airport_delay_status or airport.get_delay_status. |
| query | string | yes | Search query used to find tracked airports. |
No examples provided.
get_airport_delay_status Get airport delay status ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | Resolved airport IATA code. |
| detailsUrl | string | yes | Pro Flight Search airport details URL for citation or follow-up. |
| disclaimer | string | yes | Operational-data disclaimer for the airport status. |
| format | string | yes | Returned text format. |
| scope | string | yes | Current data scope for the tool result. |
| statusText | string | yes | Airport status text returned in the MCP content block. |
No examples provided.
search_supported_airports Search supported airports ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Airport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | Tracked airport matches that can be used with get_airport_delay_status or airport.get_delay_status. |
| query | string | yes | Search query used to find tracked airports. |
No examples provided.