mcp-registry/com.proflightsearch/airport-delays · v1.0.2
Also listed as pulsemcp/pro-flight-search
As of 2026-10-20 10:25 UTC, the Proflightsearch Airport Delays MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 7 minutes.
Read-only airport delay, weather, and 24h forecast tools for AI assistants. Airport-level only.
Claude Code
claude mcp add --transport http proflightsearch-airport-delays-mcp-serve https://proflightsearch.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"proflightsearch-airport-delays-mcp-serve": {
"type": "http",
"url": "https://proflightsearch.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
Handshake + tools/list takes ~1,736 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.proflightsearch%2Fairport-delays/fixes
{
"name": "airport_get_delay_status",
"description": "Get live airport-level delay, cancellation, and weather flight-rules for one airport. Accepts IATA code, city, or airport name. Alias of get_airport_delay_status for clients that prefer dot-notation tool names.",
"inputSchema": {
"type": "object",
"required": [
"airport"
],
"properties": {
"format": {
"enum": [
"plain",
"markdown"
],
"type": "string",
"description": "Output format. Use plain for SMS-style replies; markdown includes formatted links. Defaults to plain."
},
"airport": {
"type": "string",
"description": "Airport IATA code, city, or airport name. Examples: JFK, LHR, Copenhagen, Chicago O'Hare."
}
}
},
"annotations": {
"title": "Get airport delay status",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Get airport delay status"
}{
"name": "airport_search_supported",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Airport code, city, or airport name to search. Examples: London, Paris, Chicago, ORD."
}
}
},
"annotations": {
"title": "Search supported airports",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Search supported airports"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.proflightsearch/airport-delays"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.proflightsearch/airport-delays"}) over MCP.
airport.get_delay_status ~178 tokensget_airport_delay_status ~168 tokenssearch_supported_airports ~136 tokensairport.search_supported ~135 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.proflightsearch%2Fairport-delays?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.proflightsearch%2Fairport-delays?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.proflightsearch%2Fairport-delays.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.proflightsearch%2Fairport-delays.svg :target: https://glimind.com/server/mcp-registry%2Fcom.proflightsearch%2Fairport-delays?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fed0c11a1cfa0bcf…, first seen 2026-10-17, included at leaf 14367 of 32,333. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 10:25 UTC, the Proflightsearch Airport Delays MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 7 minutes.
Proflightsearch Airport Delays MCP server advertises 4 tools, including airport.get_delay_status, airport.search_supported, get_airport_delay_status, search_supported_airports.
Point your MCP client at this streamable-http endpoint: https://proflightsearch.com/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.