Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Korea Flight is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
14 Korean airports flight info + Incheon arrival/departure congestion + facility search.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http korea-flight-mcp https://korea-flight.kimnchai.com/mcp
# 2 — ask your agent for something these tools do
# get_flight_status, search_by_route, track_my_flight and 5 more
Korea Flight costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http korea-flight-mcp https://korea-flight.kimnchai.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
[한국 공항 실시간 운항정보] 한국 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 편명·목적지
| Parameter | Type | Required | Notes |
|---|---|---|---|
| airport | string | no | — |
| direction | string | no | — |
| flight_date | no | — | |
| lang | string | no | — |
[한국 공항 실시간 운항정보] 두 공항 사이 오늘 운항편을 검색합니다 (양방향, 한쪽은 한국 공항). 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") Arg
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | — |
| destination | string | yes | — |
| lang | string | no | — |
[한국 공항 실시간 운항정보] 편명을 추적해 예정/변경 시각, 게이트, 수취대, 상태를 알려줍니다. (픽업에 유용) 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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flight_id | string | yes | — |
| hub_airport | string | no | — |
| lang | string | no | — |
[한국 공항 실시간 운항정보] 공항 오늘 개요 — 운항량, 상위 항공사·노선, 터미널 분포. 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: (op
| Parameter | Type | Required | Notes |
|---|---|---|---|
| airport | string | yes | — |
| terminal | string | no | — |
| lang | string | no | — |
[한국 공항 실시간 운항정보] 인천공항편의 코드쉐어 정보 — 마스터편명·파트너편 (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) l
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flight_id | string | yes | — |
| lang | string | no | — |
[한국 공항 실시간 운항정보] 인천공항 입국 도착 정보 (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")
| Parameter | Type | Required | Notes |
|---|---|---|---|
| terno | string | no | — |
| airport | string | no | — |
| flight_id | string | no | — |
| lang | string | no | — |
[한국 공항 실시간 운항정보] 인천공항 출국장 혼잡도 (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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| terminal | string | no | — |
| lang | string | no | — |
[한국 공항 실시간 운항정보] 인천공항 입점 상업시설(매장·서비스) 정보 — 약 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"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| area | string | no | — |
| lang | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Korea Flight or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_flight_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_by_route | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| track_my_flight | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| airport_overview | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| codeshare_info | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| incheon_arrivals | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| incheon_departure_congestion | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| incheon_facilities | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Korea Flight can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.