J
joelynli0110/open-transfer-times
Is this flight connection comfortable, tight, or risky?
更新 2026-11-18
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · joelynli0110/open-transfer-times · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
joelynli0110/open-transfer-times;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Open Transfer Times
以下摘录自该仓库的 README(片段)
Is this flight connection comfortable, tight, or risky? Open, cited airport
transfer data, an engine that explains its verdict, and an MCP server so AI
agents can check connections before recommending a flight.
## Try it
Ask an AI agent to compare layovers. With the MCP server connected, it gets:
text
1. IST 3 h BER–IST–PVG: RECOMMEND — rated comfortable, margin 135 min, protected itinerary, medium confidence
2. VIE 2 h BER–VIE–PVG: INSUFFICIENT DATA — estimate only, margin 65 min, protected itinerary, low confidence
Why: Key information is missing, so the rating cannot be relied on. No transfer profile for this airport; generic baseline allowances were used.
3. FRA 50 min BER–FRA–PVG: AVOID — rated risky, margin -5 min, protected itinerary, medium confidence
Why: The transfer steps take about as long as the layover or longer.
Only RECOMMEND and CAUTION options may be presented as workable; for the others, say why.
Vienna has plenty of time but no airport data, so it is not recommended. Each
result gives a decision, the transfer steps it counted, a confidence level, and
the official sources behind the airport data:
text
BER–LHR–PVG: CAUTION — The terminals are not known, and a terminal change would leave little or no margin; ask for the terminals.
Rating: REASONABLE — A practical connection on one ticket.
Confidence: MEDIUM — The terminals are not known; a terminal change would make this connection tight or risky. With a terminal change (25 min) the margin would be 10 min (tight). The transfer-step durations are rule-of-thumb estimates, not sourced figures.
Layover 90 min, transfer steps 55 min, margin 10 to 35 min (tight if every possible step applies).
Steps counted: Move through airport 40 min (heuristic); Allow for another security check 15 min (heuristic). No other steps were counted.
Possible step not counted: Change terminals 25 min (terminals not given). Give the margin as a range and ask for the missing detail if it matters.
### With Claude Desktop or any MCP client
Add to claude_desktop_config.json, then fully restart Claude:
json
"mcpServers": {
"open-transfer-times": { "command": "npx", "args": ["-y", "open-transfer-times-mcp"] }
Then ask, in a new chat: "From Berlin to Shanghai, which is safest: 50 minutes
in Frankfurt, 3 hours in Istanbul or 2 hours in Vienna?"
With a flight search. Add a flight-search MCP server such as
fli next to it, and ask "Find flights
from Berlin to Shanghai on 21 December. I prefer cheap ones, but no risky
connections." The agent searches, checks every connection, and ranks the
results by risk as well as price: docs/demo-flight-search.md.
The server is also listed in the official MCP Registry
and on Glama.
Tools and options: packages/mcp.
### From code
bash
npm install open-transfer-times
js
const { assessConnection } = require("open-transfer-times");
const result = assessConnection(
{ segments: [
{ origin: "BER", destination: "LHR", arrivalTime: "2026-09-20T10:00" },
{ origin: "LHR", destination: "PVG", departureTime: "2026-09-20T11:30" }
] },
{ ticketStatus: "protected" }
);
result.quality; // "reasonable"
result.confidence.level; // "medium"
API reference: packages/core.
## Why this exists
transfer data, an engine that explains its verdict, and an MCP server so AI
agents can check connections before recommending a flight.
## Try it
Ask an AI agent to compare layovers. With the MCP server connected, it gets:
text
1. IST 3 h BER–IST–PVG: RECOMMEND — rated comfortable, margin 135 min, protected itinerary, medium confidence
2. VIE 2 h BER–VIE–PVG: INSUFFICIENT DATA — estimate only, margin 65 min, protected itinerary, low confidence
Why: Key information is missing, so the rating cannot be relied on. No transfer profile for this airport; generic baseline allowances were used.
3. FRA 50 min BER–FRA–PVG: AVOID — rated risky, margin -5 min, protected itinerary, medium confidence
Why: The transfer steps take about as long as the layover or longer.
Only RECOMMEND and CAUTION options may be presented as workable; for the others, say why.
Vienna has plenty of time but no airport data, so it is not recommended. Each
result gives a decision, the transfer steps it counted, a confidence level, and
the official sources behind the airport data:
text
BER–LHR–PVG: CAUTION — The terminals are not known, and a terminal change would leave little or no margin; ask for the terminals.
Rating: REASONABLE — A practical connection on one ticket.
Confidence: MEDIUM — The terminals are not known; a terminal change would make this connection tight or risky. With a terminal change (25 min) the margin would be 10 min (tight). The transfer-step durations are rule-of-thumb estimates, not sourced figures.
Layover 90 min, transfer steps 55 min, margin 10 to 35 min (tight if every possible step applies).
Steps counted: Move through airport 40 min (heuristic); Allow for another security check 15 min (heuristic). No other steps were counted.
Possible step not counted: Change terminals 25 min (terminals not given). Give the margin as a range and ask for the missing detail if it matters.
### With Claude Desktop or any MCP client
Add to claude_desktop_config.json, then fully restart Claude:
json
"mcpServers": {
"open-transfer-times": { "command": "npx", "args": ["-y", "open-transfer-times-mcp"] }
Then ask, in a new chat: "From Berlin to Shanghai, which is safest: 50 minutes
in Frankfurt, 3 hours in Istanbul or 2 hours in Vienna?"
With a flight search. Add a flight-search MCP server such as
fli next to it, and ask "Find flights
from Berlin to Shanghai on 21 December. I prefer cheap ones, but no risky
connections." The agent searches, checks every connection, and ranks the
results by risk as well as price: docs/demo-flight-search.md.
The server is also listed in the official MCP Registry
and on Glama.
Tools and options: packages/mcp.
### From code
bash
npm install open-transfer-times
js
const { assessConnection } = require("open-transfer-times");
const result = assessConnection(
{ segments: [
{ origin: "BER", destination: "LHR", arrivalTime: "2026-09-20T10:00" },
{ origin: "LHR", destination: "PVG", departureTime: "2026-09-20T11:30" }
] },
{ ticketStatus: "protected" }
);
result.quality; // "reasonable"
result.confidence.level; // "medium"
API reference: packages/core.
## Why this exists
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/joelynli0110-open-transfer-times/)
- 来源
- awesome · https://github.com/joelynli0110/open-transfer-times
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。