Korea Flight MCP
REMOTE · KOREA-FLIGHT.KIMNCHAI.COM · SCANNED SEP 20
14 Korean airports flight info + Incheon arrival/departure congestion + facility search.
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 → Why this is hard to score →
Endpoint Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2141 tokens (~267/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the Korea Flight MCP server?
Korea Flight MCP is a hosted endpoint at https://korea-flight.kimnchai.com/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 · korea-flight.kimnchai.com
claude mcp add --transport http kimnchai-korea-flight-mcp 'https://korea-flight.kimnchai.com/mcp'
{
"mcpServers": {
"kimnchai-korea-flight-mcp": {
"url": "https://korea-flight.kimnchai.com/mcp"
}
}
} {
"servers": {
"kimnchai-korea-flight-mcp": {
"type": "http",
"url": "https://korea-flight.kimnchai.com/mcp"
}
}
} [mcp_servers.kimnchai-korea-flight-mcp] url = "https://korea-flight.kimnchai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kimnchai-korea-flight-mcp": {
"type": "remote",
"url": "https://korea-flight.kimnchai.com/mcp",
"enabled": true
}
}
} openclaw mcp add kimnchai-korea-flight-mcp --url 'https://korea-flight.kimnchai.com/mcp' --transport streamable-http
mcp_servers:
kimnchai-korea-flight-mcp:
url: "https://korea-flight.kimnchai.com/mcp" {
"McpServers": {
"kimnchai-korea-flight-mcp": {
"Transport": "http",
"Url": "https://korea-flight.kimnchai.com/mcp"
}
}
} assistant mcp add kimnchai-korea-flight-mcp -t streamable-http -u 'https://korea-flight.kimnchai.com/mcp'
{
"mcpServers": {
"kimnchai-korea-flight-mcp": {
"type": "http",
"url": "https://korea-flight.kimnchai.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.
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 −1
- Stability: pass → 0.93 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Aug 26 71
- Tool “get_flight_status” rewrote its description, which is the text the model reads security
- 11 Aug 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
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 20 Sept 2026 · Probed https://korea-flight.kimnchai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kimnchai.com | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | cab1152e927520e60e7cdbc73356279a |
| SANs: kimnchai.com, *.kimnchai.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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of korea-flight.kimnchai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kimnchai.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://korea-flight.kimnchai.com/mcp | Verified | 200 | |
| http (plaintext) | http://korea-flight.kimnchai.com/mcp | Inconclusive | 406 |
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 →
airport_overview ~298
[한국 공항 실시간 운항정보] 공항 오늘 개요 — 운항량, 상위 항공사·노선, 터미널 분포. Airport overview — today's volume, top airlines/routes, terminal split (ICN only). Useful for first-time visitors. Examples: - "What's GMP like?" → airport_overview("GMP") - "ICN T1 departures" → airport_overview("ICN", "T1") # T1 → P01 자동 변환 Args: airport: Airport IATA (e.g. GMP, ICN, CJU) terminal: (optional) Terminal ID. ICN 만 의미. 다음 입력 모두 허용: - "T1"/"T2"/"터미널1"/"터미널2"/"1"/"2" → 내부적으로 P01/P03 으로 자동 변환 - "탑승동"/"concourse" → P02 - "P01"/"P02"/"P03" 정식 코드 그대로 ICN 외 공항에선 무시됨. lang: Response language 'E' (default) / 'K' / 'C' / 'J'. Match user's language.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | yes | – |
| lang | string | – | – |
| terminal | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
codeshare_info ~179
[한국 공항 실시간 운항정보] 인천공항편의 코드쉐어 정보 — 마스터편명·파트너편 (ICN 전용). Codeshare info for ICN flights — master flight number + codeshare partners. ICN-only (other airports don't provide codeshare data). Examples: - "Is OZ117 a codeshare?" → codeshare_info("OZ117") - "Master flight of ET1291?" → codeshare_info("ET1291") Args: flight_id: Flight number (e.g. OZ117, ET1291) lang: Response language 'E' (default) / 'K' / 'C' / 'J'. Match user's language.
| Name | Type | Req | Description |
|---|---|---|---|
| flight_id | string | yes | – |
| lang | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_flight_status ~384
[한국 공항 실시간 운항정보] 한국 14개 공항의 실시간 출도착 정보를 조회합니다. Look up real-time arrival/departure status for 14 Korean airports. Rendering: every line already carries the gate ('게이트 267' / 'Gate 267'), the terminal, and — for departures — the check-in counter ('체크인 A B C D' / 'check-in B01-B18'). When you render a table, give the gate AND the check-in counter their own columns next to 편명·목적지·시각·상태·터미널 — do not drop them. A departing passenger moves check-in → security → gate, so a table without those two sends them back to ask again. '-' means not assigned yet; show '-' rather than inventing or guessing a gate or counter. Args: airport: Airport IATA (ICN/GMP/PUS/CJU/TAE/CJJ etc., 14 total) direction: 'arrival' or 'departure' flight_date: date — omit or 'today' for live; 'yesterday'/'YYYY-MM-DD' for snapshot. Up to 30 days back. ICN historical data only on dates the nightly snapshot ran. lang: Response language — 'E' English (default) / 'K' 한국어 / 'C' 中文 / 'J' 日本語. MUST be filled to match user's language: 한국어 질문이면 'K', 中文이면 'C', 日本語면 'J'. Default 'E' is the safest pivot for any other language.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | – | – |
| direction | string | – | – |
| flight_date | – | – | – |
| lang | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
incheon_arrivals ~310
[한국 공항 실시간 운항정보] 인천공항 입국 도착 정보 (H-2~H+2 시간 윈도우). 편명·도착시간·게이트·입국장(A-F)·내외국인 수. Incheon Airport arrival info (H-2~H+2 window). Per-flight schedule/actual time, aircraft gate, entry gate (A-F), domestic/foreign passenger counts. Examples: - "How busy is Incheon T1 arrivals right now?" → incheon_arrivals(terno="T1") - "Any arrivals from Hanoi?" → incheon_arrivals(airport="HAN") - "Where is VN416 arriving?" → incheon_arrivals(flight_id="VN416") Args: terno: Terminal filter — 'T1' / 'T2' / '' (all). Default ''. airport: Origin airport IATA filter (e.g., HAN, NRT). Default '' (all). flight_id: Specific flight ID filter (e.g., 'VN416'). Default '' (all). lang: Response language — 'E' English (default) / 'K' 한국어 / 'C' 中文 / 'J' 日本語. MUST match user's language.
| Name | Type | Req | Description |
|---|---|---|---|
| airport | string | – | – |
| flight_id | string | – | – |
| lang | string | – | – |
| terno | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
incheon_departure_congestion ~205
[한국 공항 실시간 운항정보] 인천공항 출국장 혼잡도 (1분 주기 실시간). 출국장 게이트별 대기인원 + 발생일시. Incheon Airport departure hall congestion (1-min real-time). Per-gate wait count. T1 (P01) currently available; T2 (P02) coming soon per data.go.kr. Examples: - "How crowded is Incheon T1 departure right now?" → incheon_departure_congestion(terminal="T1") Args: terminal: 'T1' (or 'P01') — Terminal 1. 'T2'/'P02' pending data.go.kr release. lang: Response language — 'E' (default) / 'K' / 'C' / 'J'. Match user's language.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| terminal | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
incheon_facilities ~280
[한국 공항 실시간 운항정보] 인천공항 입점 상업시설(매장·서비스) 정보 — 약 1,227개. dataset 15095043 (B551177 family). Incheon Airport commercial facilities (~1,227 stores/services). Filter by query. Examples: - "Where is Starbucks at Incheon?" → incheon_facilities(query="Starbucks") - "면세점 어디 있어?" → incheon_facilities(query="면세점", lang="K") - "Toilets in departure area?" → incheon_facilities(query="Toilet", area="departure") - "출국장 음식점" → incheon_facilities(query="식당", area="departure", lang="K") Args: query: Facility name / item / location filter (case-insensitive partial match). '' = top by area. area: 'arrival' (A=입국장) / 'departure' (D=출국장) / '' (all). lang: 'E' English (default — uses EN endpoint) / 'K' 한국어 (uses KR endpoint). C/J fall back to English.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | – |
| lang | string | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_by_route ~228
[한국 공항 실시간 운항정보] 두 공항 사이 오늘 운항편을 검색합니다 (양방향, 한쪽은 한국 공항). Find today's flights between an origin and a destination airport. Bidirectional — at least one side must be a Korean hub. Examples: - "GMP→CJU schedule" → search_by_route("GMP", "CJU") - "Flights from Vancouver to Incheon" → search_by_route("YVR", "ICN") - "ICN→Narita flights" → search_by_route("ICN", "NRT") Args: origin: Origin airport IATA (e.g. GMP, ICN, YVR) destination: Destination airport IATA (e.g. CJU, NRT, ICN) lang: Response language 'E' (default) / 'K' / 'C' / 'J'. Match user's language.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| lang | string | – | – |
| origin | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
track_my_flight ~257
[한국 공항 실시간 운항정보] 편명을 추적해 예정/변경 시각, 게이트, 수취대, 상태를 알려줍니다. (픽업에 유용) Track a flight — scheduled/estimated times, gate, baggage carousel, status. Carousel is critical for airport pickup. Examples: - "Is KE093 delayed?" → track_my_flight("KE093") - "7C166 arrival time & carousel" → track_my_flight("7C166") - "BX804F departure gate" → track_my_flight("BX804F", "GMP") Args: flight_id: Flight number (e.g. KE093, 7C166, BX804F) hub_airport: Hub airport IATA. If known, narrows search. Empty triggers 30-day snapshot DB lookup → falls back to 4-hub fan-out. lang: Response language 'E' (default) / 'K' / 'C' / 'J'. Match user's language.
| Name | Type | Req | Description |
|---|---|---|---|
| flight_id | string | yes | – |
| hub_airport | string | – | – |
| lang | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Korea Flight MCP server?
Korea Flight MCP is listed in the public MCP registry as io.github.kimnchai/korea-flight-mcp. 14 Korean airports flight info + Incheon arrival/departure congestion + facility search. This page covers its hosted endpoint (https://korea-flight.kimnchai.com/mcp).
Is the Korea Flight MCP server safe to use?
Korea Flight MCP scores 74 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 Korea Flight MCP server expose?
Korea Flight MCP exposes 8 tools: get_flight_status, search_by_route, track_my_flight, airport_overview, codeshare_info, and 3 more. Their descriptions and schemas cost roughly 2,141 tokens of context every time the server is loaded.
Does the Korea Flight MCP server require authentication?
No. We connected to Korea Flight MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Korea Flight MCP server still maintained?
Korea Flight MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.