korail-mcp
Related Servers
Alternatives to korail-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI to query real-time Korean public data including weather, real estate prices, air quality, economic indicators, and business registration via natural language.1MIT
- AlicenseAqualityCmaintenanceEnables natural language querying of Korean statistical data from KOSIS, including population, employment, GDP, housing prices, and more, with support for regional and trend analysis.813 npm17MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to retrieve real-time official Korean statistics from the KOSIS database through natural language queries, with source citations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to query Korean public linked data sources, follow relationships between records, and retrieve original source attributes with evidence and explicit failure reporting.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Korean official statistics from KOSIS via natural language in MCP clients like Claude Desktop, wrapping the KOSIS OpenAPI for search, data retrieval, and metadata exploration.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to access South Korean tourism information via the official Korea Tourism Organization API, providing comprehensive search for attractions, events, food, and accommodations with multilingual support.832 PyPI9MIT
TDQS
Scored across 98 tools
There are several clusters of tools with unclear boundaries, such as get_station_facilities, get_accessible_facilities, get_station_facilities_detail, and the get_urban_* facility tools, which all cover similar physical station amenities from different sources. More seriously, get_mainline_carriage overlaps heavily with get_mainline_station_per, and get_wide_area_carriage overlaps with get_wide_rail_station_per, so an agent can easily select the wrong endpoint.
The set mostly uses English snake_case with get_/search_/list_/decode_ prefixes, so the broad pattern is readable. However, analogous tools are named inconsistently: get_mainline_carriage vs get_mainline_station_per, get_transport_stat_codes vs get_train_codes, and search_loading_time_adjustment vs list_standard_loading_time all use different verb/object conventions for similar lookup operations.
98 tools is an extreme size for a single MCP server and far exceeds the 50+ threshold for a coherence failure. Even if KORAIL has many datasets, the server should be split into focused sub-servers by domain such as urban rail, mainline operations, freight, station facilities, or corporate administration.
Read-only coverage is broad, but there are significant gaps for a KORAIL information server: current passenger fare lookup is missing, real-time train status/delay information is absent, and some datasets are only snapshots or single-day samples such as get_train_run_history. The many duplicated station and facilities datasets also make it unclear whether a query is fully answered without checking multiple tools.