_ registry / mcp streamable-http · checked 3h ago

airport-transit

https://airport-transit.kimnchai.com

Registry code: a6eb75245a8cfa1b

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://airport-transit.kimnchai.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is airport-transit live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is airport-transit free to use?
Yes — the hub reached it with no key and no payment.
What tools does airport-transit have?
5 tools: airport_bus, airport_shuttle_next, airport_shuttle_schedule, airport_taxi, airport_train.
Is airport-transit safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.5%· all time 99.5%

latency
895ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 430 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get incheon airport bus timetables
  • get arex train schedule
  • check airport taxi queue
  • get next airport shuttle arrival
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 open 5 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • airport_bus reads open 10h ago

    [인천공항 대중교통] 인천국제공항 ↔ 전국 공항버스 노선·시간표·요금·승차장. 데이터셋 갱신 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}]}

    mcp-tool

    {
      "type": "object",
      "title": "airport_busArguments",
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "ko"
        },
        "region": {
          "type": "string",
          "title": "Region",
          "default": ""
        },
        "search": {
          "type": "string",
          "title": "Search",
          "default": ""
        }
      }
    }
    arguments 21 lines
  • airport_shuttle_next reads open 10h ago

    [인천공항 대중교통] 인천공항 무료 셔틀버스 다음 도착 예측 시간(분). 공항 내부 이동용 무료 셔틀 (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}]}

    mcp-tool

    {
      "type": "object",
      "title": "airport_shuttle_nextArguments",
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "ko"
        },
        "stop": {
          "type": "string",
          "title": "Stop",
          "default": ""
        },
        "route": {
          "type": "string",
          "title": "Route",
          "default": ""
        }
      }
    }
    arguments 21 lines
  • airport_shuttle_schedule reads open 10h ago

    [인천공항 대중교통] 인천공항 무료 셔틀버스 시간표 (의미 단위 요약). 노선별 평일/휴일 첫차·막차·배차 간격·운행 편수 + 종점 출발 시각 전체 + 첫편의 정류장 순서별 통과 시각. 정류장×편수 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}, ...] } }}

    mcp-tool

    {
      "type": "object",
      "title": "airport_shuttle_scheduleArguments",
      "properties": {
        "day": {
          "type": "string",
          "title": "Day",
          "default": "all"
        },
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "ko"
        },
        "route": {
          "type": "string",
          "title": "Route",
          "default": ""
        }
      }
    }
    arguments 21 lines
  • airport_taxi reads open 3h ago

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

    mcp-tool

    {
      "type": "object",
      "title": "airport_taxiArguments",
      "properties": {
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "ko"
        },
        "terminal": {
          "type": "string",
          "title": "Terminal",
          "default": "T1"
        }
      }
    }
    arguments 16 lines
  • airport_train reads open 3h ago

    [인천공항 대중교통] 인천공항 공항철도 (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).

    mcp-tool

    {
      "type": "object",
      "title": "airport_trainArguments",
      "properties": {
        "date": {
          "type": "string",
          "title": "Date",
          "default": ""
        },
        "lang": {
          "type": "string",
          "title": "Lang",
          "default": "ko"
        },
        "type": {
          "type": "string",
          "title": "Type",
          "default": ""
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 5
        },
        "station": {
          "type": "string",
          "title": "Station",
          "default": ""
        },
        "train_no": {
          "type": "string",
          "title": "Train No",
          "default": ""
        }
      }
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a6eb75245a8cfa1b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a6eb75245a8cfa1b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a6eb75245a8cfa1b/badge.svg)](https://brick.blue/agent/a6eb75245a8cfa1b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on kimnchai.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.