Open Transfer Times
NPM · OPEN-TRANSFER-TIMES-MCP
Check if a flight connection is comfortable, tight or risky, with cited airport data.
Available components
Last scanned (5 minutes ago)
Scores higher than 59% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1184 tokens (~296/item across 4 items; 4 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 Management70
- Stability observed for 21 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 22 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 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.
- 16 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.
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.0 → 0.4.0 functional
- 12 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.
- 10 Nov 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
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 22 Nov 2026 · Analysed npm/open-transfer-times-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_connection Check a flight connection ~570
Assess one one-stop flight connection: does the layover leave enough time to transfer? Use it for a single itinerary; to compare two or more options, use compare_connections once instead of calling this tool for each. Deducts the transfer steps that apply at the connection airport (walking, Schengen passport control, terminal change, security re-screening, baggage re-check) from the layover and returns a decision (recommend / caution / insufficient_data / avoid), a rating (comfortable / reasonable / tight / risky), confidence with reasons, ticket exposure and cited airport facts. Give arrival and departure as local times at the connection airport, or only layover_minutes when that is all the user said. Deterministic and offline: no flight data, no delay prediction. Explain only the returned steps; airport facts apply only where their scope matches the trip.
| Name | Type | Req | Description |
|---|---|---|---|
| arrival_terminal | string | – | Arrival terminal at the connection airport, if known |
| arrival_time | string | – | Scheduled arrival of the first flight at the connection airport, local time, YYYY-MM-DDTHH:mm. Give both times, or layover_minutes instead. |
| baggage_recheck | boolean | – | true if checked bags must be collected and checked in again, false if not (hand luggage only, or bags checked through). On separate tickets, leave it out only if unknown: the result then says whether… |
| departure_terminal | string | – | Departure terminal at the connection airport, if known |
| departure_time | string | – | Scheduled departure of the second flight from the connection airport, local time, YYYY-MM-DDTHH:mm. Give both times, or layover_minutes instead. |
| from | string | yes | Origin airport of the first flight (IATA), e.g. BER |
| inbound_airline | string | – | IATA code of the airline operating the first flight (e.g. LH), if known. Used to decide whether an airline's minimum connection time applies. |
| layover_minutes | integer | – | Scheduled time between arrival and departure, in minutes. Use this when the user gives only a layover duration; do not invent dates or clock times. |
| outbound_airline | string | – | IATA code of the airline operating the second flight, if known. |
| terminal_change | boolean | – | true if the user knows they change terminals, false if they know they do not. Leave out if unknown: the result then shows the margin with a possible terminal change. |
| ticket | string | – | protected = both flights on one ticket/booking; separate = self-transfer on separate tickets; unknown if not stated |
| to | string | yes | Destination airport of the second flight (IATA), e.g. PVG |
| via | string | yes | Connection airport (IATA), e.g. IST |
| Name | Type | Req | Description |
|---|---|---|---|
| baggage_recheck | string | yes | – |
| buffer_minutes | number | yes | – |
| confidence | object | yes | How far the estimate can be trusted, independent of the quality rating. Low means key information is missing. |
| connection_airport | object | yes | – |
| decision | object | yes | What to do with this connection. insufficient_data means key information is missing: ask the user rather than recommending it. |
| disclaimer | string | yes | – |
| factors | array | yes | – |
| if_baggage_recheck | object | – | Separate tickets with unknown bags: the result if bags must be re-checked. |
| layover_basis | string | yes | How the layover length was computed: the airport's time zone, explicit UTC offsets, plain clock difference, or a given duration. |
| layover_minutes | number | yes | – |
| layover_source | string | yes | – |
| mct | object | yes | Published minimum connection times at this airport, separate from the structural estimate. Whether a scoped MCT applies to this trip is unknown, so meets_published does not prove the airline would se… |
| possible_steps | array | yes | Steps that may apply but could not be determined. They are not in steps or buffer_minutes; worst_case adds them. |
| quality | string | yes | – |
| route | string | yes | – |
| steps | array | yes | – |
| terminal_change | string | yes | unknown: terminals were not given at an airport where changing terminals takes time; see possible_steps. |
| ticket | object | yes | – |
| transfer_process_minutes | number | yes | – |
| verdict | string | yes | – |
| wall_clock_layover_minutes | number | – | Present when clocks change during the layover: what the local clocks show. |
| worst_case | object | – | The margin if every possible step applies. buffer_minutes is the best case. |
No examples provided.
compare_connections Compare and rank flight connections ~152
Compare and rank 2–20 one-stop itineraries (for example flight search results, or options the user lists) from safest to riskiest connection. Use it whenever the user weighs options; for a single itinerary use check_connection. Ranks by decision (recommend, caution, insufficient data, avoid), then transfer quality, then ticket protection (one ticket before unknown before self-transfer), then confidence, then remaining margin, and says why each option that is not recommended is not. Each option takes times or layover_minutes, like check_connection; the optional id maps results back to your own options (e.g. an offer id or price).
| Name | Type | Req | Description |
|---|---|---|---|
| options | array | yes | Two to twenty itineraries to compare |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | yes | – |
| ranked | array | yes | – |
No examples provided.
get_airport_profile Get an airport's transfer profile ~102
Return one airport's transfer allowances, whether each is a heuristic estimate or sourced, and the cited facts (with official source links) about transferring there. Use it to answer questions about an airport itself or to show sources; to judge a specific connection use check_connection, and to see which airports have a profile use list_airports. Airports without a profile return the standard baseline.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | IATA airport code, e.g. LHR |
| Name | Type | Req | Description |
|---|---|---|---|
| allowances | array | yes | – |
| coverage | string | yes | – |
| facts | array | yes | – |
| has_profile | boolean | yes | – |
| iata | string | yes | – |
| last_reviewed | string | – | – |
| name | string | – | – |
No examples provided.
list_airports List airports with transfer profiles ~70
List the airports that have their own transfer profile, with how well each is sourced. Use it to tell the user where results are better supported; for one airport's allowances and sources use get_airport_profile. Every other airport is still accepted by the assessment tools, with the standard baseline and low confidence.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| airports | array | yes | – |
No examples provided.
How do I install the Open Transfer Times MCP server?
Open Transfer Times runs locally as an npm package, launched with npx -y open-transfer-times-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · open-transfer-times-mcp
claude mcp add joelynli0110-open-transfer-times -- npx -y open-transfer-times-mcp
What is the Open Transfer Times MCP server?
Open Transfer Times is an MCP server listed in the public MCP registry as io.github.joelynli0110/open-transfer-times. Check if a flight connection is comfortable, tight or risky, with cited airport data. This page covers its npm package (open-transfer-times-mcp).
Is the Open Transfer Times MCP server safe to use?
Open Transfer Times scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. 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 Open Transfer Times MCP server expose?
Open Transfer Times exposes 4 tools: check_connection, compare_connections, get_airport_profile, list_airports. Their descriptions and schemas cost roughly 894 tokens of context every time the server is loaded.
Is the Open Transfer Times MCP server still maintained?
Open Transfer Times is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Open Transfer Times MCP server under?
Open Transfer Times declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Open Transfer Times MCP server?
VerifyMCP ran 16 checks on Open Transfer Times, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.