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.

Incheon Airport Transit MCP

REMOTE · AIRPORT-TRANSIT.KIMNCHAI.COM · SCANNED SEP 21

Incheon Airport (ICN) transit: limo buses, internal shuttles, taxi queues, AREX train schedule.

0 this week 75 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1511 tokens (~302/item across 5 items; 5 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 5 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
Install

How do I install the Incheon Airport Transit MCP server?

Incheon Airport Transit MCP is a hosted endpoint at https://airport-transit.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 · airport-transit.kimnchai.com

# add to Claude Code
claude mcp add --transport http kimnchai-airport-transit-mcp 'https://airport-transit.kimnchai.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "kimnchai-airport-transit-mcp": {
      "url": "https://airport-transit.kimnchai.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "kimnchai-airport-transit-mcp": {
      "type": "http",
      "url": "https://airport-transit.kimnchai.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.kimnchai-airport-transit-mcp]
url = "https://airport-transit.kimnchai.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kimnchai-airport-transit-mcp": {
      "type": "remote",
      "url": "https://airport-transit.kimnchai.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add kimnchai-airport-transit-mcp --url 'https://airport-transit.kimnchai.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  kimnchai-airport-transit-mcp:
    url: "https://airport-transit.kimnchai.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "kimnchai-airport-transit-mcp": {
      "Transport": "http",
      "Url": "https://airport-transit.kimnchai.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add kimnchai-airport-transit-mcp -t streamable-http -u 'https://airport-transit.kimnchai.com/mcp'
// mcp.json
{
  "mcpServers": {
    "kimnchai-airport-transit-mcp": {
      "type": "http",
      "url": "https://airport-transit.kimnchai.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Sept 26 +1
    • Stability: 0.97 → pass security
  • 2 Sept 26 −1
    • Stability: pass → 0.97 functional
  • 26 Aug 26 +2
    • 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 0
    • Stability: 0.97 → pass security
  • 24 Aug 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.

  • 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
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 4 Aug 26 0
    • HSTS header: unverified → fail security
    • HTTPS: pass → unverified security
    • Authorization: unverified → partial security
    • Endpoint reachability: unreachable → reachable functional
    • Tool coverage: unverified → 100 functional
    • Stability: unverified → 0.30 functional
    • MCP protocol: unverified → pass 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 Sept 2026 · Probed https://airport-transit.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 airport-transit.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://airport-transit.kimnchai.com/mcp Verified 200
http (plaintext) http://airport-transit.kimnchai.com/mcp Inconclusive 406
MCP tools · 5 exposed · ~1,511 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
airport_bus ~247

[인천공항 대중교통] 인천국제공항 ↔ 전국 공항버스 노선·시간표·요금·승차장. 데이터셋 갱신 60분. T1/T2 평일·주말 시간표 분리 제공. 버스 등급(일반/우등)·운수사 연락처 포함. Args: region: 한글 권역명(서울/경기/인천/강원/충청/경상/전라) 또는 1~7 코드. 빈값=전체. search: 버스번호/운수사/정류장 키워드 부분일치 (예: "강남", "6009", "KAL"). lang: "ko" (한글) 또는 "en" (영문 라벨 일부). Returns: {count, area, items: [{busnumber, route, fare, busclass, cpname, terminal_first_last, route_info, ride_loc}]}

NameTypeReqDescription
langstring
regionstring
searchstring

Structured output declared, but exposes no named fields.

No examples provided.

airport_shuttle_next ~216

[인천공항 대중교통] 인천공항 무료 셔틀버스 다음 도착 예측 시간(분). 공항 내부 이동용 무료 셔틀 (T1 ↔ T2 ↔ AICC ↔ 화물청사역 등). 실시간 60분 갱신. Args: stop: 정류장 한글명(예: "제1여객터미널", "인천영종소방서") 또는 10자리 stopId. 빈값=전체. route: 노선 한글명(예: "AICC행", "AICC순환") 또는 8자리 routeId. 빈값=전체. lang: "ko"/"en". Returns: {count, items: [{stop_name, route_name, eta_minutes, ofr_time, ord, raw}]}

NameTypeReqDescription
langstring
routestring
stopstring

Structured output declared, but exposes no named fields.

No examples provided.

airport_shuttle_schedule ~426

[인천공항 대중교통] 인천공항 무료 셔틀버스 시간표 (의미 단위 요약). 노선별 평일/휴일 첫차·막차·배차 간격·운행 편수 + 종점 출발 시각 전체 + 첫편의 정류장 순서별 통과 시각. 정류장×편수 raw row 노출 (수백~수천 건) 대신 사용자 관점에서 직접 의미 있는 단위로 압축. 데이터셋 갱신 60분. 참고: 현재 시간표 dataset 에는 'AICC행' (routeId 11100001, 11100006) 두 노선만 등록되어 있어 그 외 노선(AICC순환/T1행/T2행/T2직행/ 화물청사역행/T1막차)을 필터하면 빈 결과가 정상. 도착 예측은 airport_shuttle_next 가 모든 노선 커버. Args: route: 노선 한글명(예: "AICC행") 또는 8자리 routeId. 빈값=노선 목록만 요약. day: "weekday" (평일) / "holiday" (휴일) / "all" (전체, 기본). lang: "ko"/"en". Returns: route 빈값 시: {count, routes: [{route_id, route_name, weekday_departures, holiday_departures}]} route 지정 시: {route_id, route_name, day_filter, by_day: { weekday/holiday: { day_type_kr, departure_count, first_departure, last_departure, interval_avg, all_departures: [HH:MM,...], first_trip_stops: [{stop_order, stop_name, time}, ...] } }}

NameTypeReqDescription
daystring
langstring
routestring

Structured output declared, but exposes no named fields.

No examples provided.

airport_taxi ~186

[인천공항 대중교통] 인천공항 여객터미널 택시 출차 현황 (대기수·대기시간·승차장). 1분 단위 실시간. 지역별(서울/인천/경기/인터내셔널/우등/밴) 대기 택시 수와 대기시간. Args: terminal: "T1" / "T2" / "P01" / "P03". 기본 T1. lang: "ko"/"en". Returns: {terminal, status, update_time, regions: {서울/인천/경기/인터내셔널/우등/밴: {cnt, wait_time, stand}}}

NameTypeReqDescription
langstring
terminalstring

Structured output declared, but exposes no named fields.

No examples provided.

airport_train ~436

[인천공항 대중교통] 인천공항 공항철도 (AREX) 열차 운행 정보. D-3 ~ D+3 범위. 실시간 3분 갱신. 18개 역 (서울 ↔ 인천공항T2). 일반(Comm) 모든 역 정차, 직통(Dirc) 서울↔T1/T2 무정차. 기본 동작 — date 빈값(=오늘) 이면 현재 시각(KST) 이후 출발 열차만 시간순으로 정렬해 limit 개수만 반환 ("다음 N편"). date 명시하면 그 날 처음부터 limit 개수. 18역 × 다수 열차 → D-3~D+3 전체 응답이 비대해지므로 의미 단위로 잘림. Args: station: 한글역명(예: "서울","홍대입구"), 영문, 또는 3자리 코드. 빈값=전체. train_no: 운행번호 (예: "A2046"). 빈값=전체. type: "Comm"(일반) / "Dirc"(직통) / 빈값=전체. date: YYYY-MM-DD 또는 YYYYMMDD. 빈값=오늘. limit: 반환할 최대 row 수 (기본 5, 0=전체). 응답 크기 가드. lang: "ko"/"en". Returns: {count, total_available, next_only, limit, query, items: [{drv_dt, train_no, direction, train_class, station, stop_type, plan_arrv, plan_dptr, actual_arrv, actual_dptr}]} total_available > count 이면 limit 늘려 더 보세요 (예: limit=20).

NameTypeReqDescription
datestring
langstring
limitinteger
stationstring
train_nostring
typestring

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Incheon Airport Transit MCP server?

Incheon Airport Transit MCP is listed in the public MCP registry as io.github.kimnchai/airport-transit-mcp. Incheon Airport (ICN) transit: limo buses, internal shuttles, taxi queues, AREX train schedule. This page covers its hosted endpoint (https://airport-transit.kimnchai.com/mcp).

Is the Incheon Airport Transit MCP server safe to use?

Incheon Airport Transit MCP scores 75 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 Incheon Airport Transit MCP server expose?

Incheon Airport Transit MCP exposes 5 tools: airport_bus, airport_shuttle_next, airport_shuttle_schedule, airport_taxi, airport_train. Their descriptions and schemas cost roughly 1,511 tokens of context every time the server is loaded.

Does the Incheon Airport Transit MCP server require authentication?

No. We connected to Incheon Airport Transit MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Incheon Airport Transit MCP server still maintained?

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