Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KeyFlight PNR Converter

REMOTE · KEYFLIGHT.IO

Decode Amadeus, Sabre, Galileo and Worldspan PNRs into itineraries, JSON and PRO ticket PDFs.

Available components

+3 this week 82 Trust /100

Last scanned (16 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 540 tokens (~270/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 +1

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

  • 6 Nov 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
Diagnostics

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 21 Nov 2026 · Probed https://keyflight.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=keyflight.io CN=YR1,O=Let's Encrypt,C=US 17 Nov 2026 15 Feb 2027 RSA 2048 SHA256-RSA 6f10baa19294ea9b5f33021825165966153
SANs: keyflight.io, www.keyflight.io
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of keyflight.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
keyflight.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://keyflight.io/mcp Verified 200
http (plaintext) http://keyflight.io/mcp HTTPS enforced 301 https://keyflight.io/mcp
MCP tools · 2 exposed · ~460 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
decode_pnr ~166

Decode a raw PNR into a readable itinerary (text) and structured JSON: passengers, flights, airports, terminals, times, flight duration, airline locators. Each decode with flights counts towards the monthly limit of the KeyFlight subscription, as in the PNR API.

NameTypeReqDescription
date_formatstring–"short" (18 Jun 2026) or "numeric" (18.06.2026).
textstringyesThe PNR as shown by the GDS (Amadeus, Sabre, Galileo/Apollo, Worldspan), up to 20000 characters.
time_formatstring–24 or 12 hour time. Default: 24.
viewstring–Layout of the itinerary text. Default: table.

No output schema declared.

No examples provided.

make_ticket ~294

Make a PRO e-ticket PDF (Expedia style: PNR, airline logos, class, optional price) from a raw PNR and return a link to the PDF. Passenger names and the PNR code come from the text unless given here. Included in the KeyFlight subscription.

NameTypeReqDescription
booking_classstring–Default: the cabin of the first flight's booking class.
currencystring–Currency next to the price, e.g. "USD", "€". Default: "$".
date_formatstring–"short" or "numeric".
logostring–Logo in the ticket header. Default: none.
passengersarray–Passenger names as on the ticket, e.g. "SMITH/JOHN MR". Default: the names in the PNR.
pnrstring–Booking code printed on the ticket, 5–8 letters and digits. Default: the one in the text, or a random one.
pricestring–Total price printed on the ticket, e.g. "1200.50". Default: no price on the ticket.
textstringyesThe PNR as shown by the GDS (Amadeus, Sabre, Galileo/Apollo, Worldspan), up to 20000 characters.
time_formatstring–24 or 12 hour time. Default: 24.

No output schema declared.

No examples provided.

Install

How do I install the KeyFlight PNR Converter MCP server?

KeyFlight PNR Converter is a hosted endpoint at https://keyflight.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · keyflight.io

# add to Claude Code
claude mcp add --transport http io-keyflight-pnr 'https://keyflight.io/mcp'
Common questions

What is the KeyFlight PNR Converter MCP server?

KeyFlight PNR Converter is an MCP server listed in the public MCP registry as io.keyflight/pnr. Decode Amadeus, Sabre, Galileo and Worldspan PNRs into itineraries, JSON and PRO ticket PDFs. This page covers its hosted endpoint (https://keyflight.io/mcp).

Is the KeyFlight PNR Converter MCP server safe to use?

KeyFlight PNR Converter scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the KeyFlight PNR Converter MCP server expose?

KeyFlight PNR Converter exposes 2 tools: decode_pnr, make_ticket. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.

Does the KeyFlight PNR Converter MCP server require authentication?

Yes. KeyFlight PNR Converter asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the KeyFlight PNR Converter MCP server still maintained?

KeyFlight PNR Converter is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the KeyFlight PNR Converter MCP server?

VerifyMCP ran 13 checks on KeyFlight PNR Converter, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.