korea-opendata-mcp
Related Servers
Alternatives to korea-opendata-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude to query Korean public data—holidays, weather forecasts and current conditions, air quality, and apartment transaction prices—through natural language using a single data.go.kr API key.MIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude Code to query real-time Korean weather, air quality, and monitoring station information through natural language, using public data APIs with caching and error handling.-
- AlicenseNot gradedqualityCmaintenanceBridges Korean public data APIs (data.go.kr) into MCP with automatic OpenAPI normalization, quota management, caching, and backoff. Enables natural language interaction with Korean government data through MCP.47 PyPIApache 2.0
- 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
- FlicenseAqualityDmaintenanceEnables querying Korean public datasets (apartment prices, weather, air quality) via natural language using an MCP server and local LLM agent.5-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to browse and fetch official Bank of Korea economic statistics — searching 800+ statistic tables, listing sub-series items, and pulling headline indicators like money supply, exchange rates, interest rates, CPI, GDP growth, and household debt as time series. Supports daily, monthly, quarterly, and annual series through both a hosted MCP endpoint and a local stdio server.86 npmMIT
TDQS
Scored across 12 tools
The weather pair (now vs. 3-day forecast) and the tourism pair (spots vs. festivals) are cleanly separated, and get_service_status is clearly a diagnostic meta-tool. However, four tools sit in an overlapping Bank of Korea cluster: get_base_rate, get_exchange_rate_history, get_key_statistics, and search_ecos_statistic can all surface rate/inflation/exchange-rate data, so an agent asking for 'interest rates' or 'exchange rate' has several plausible entry points (descriptions mitigate this somewhat but the boundary between the convenience tools and the raw ECOS lookup is blurry).
Every tool follows a strict snake_case verb_noun pattern: get_* for single-resource retrieval (get_base_rate, get_weather_now, get_holidays, get_subway_arrival) and search_* for query tools (search_tour_spots, search_festivals, search_ecos_statistic). No camelCase or mixed verb styles anywhere, so the action type is predictable from the name alone.
12 tools is squarely in the well-scoped range and each maps to a distinct public-data domain (weather, air quality, calendar, tourism, festivals, BOK economics, subway). Nothing feels padded: even the meta get_service_status tool earns its place as a first-stop diagnostic.
Coverage across Korean public data is broad and mostly closed-loop: current + forecast weather, air quality, holidays, tourism/festival search, economic series, and real-time subway. Minor gaps remain — no location/region-based filtering for tourism or weather, no bus or non-Seoul transit, and no detail endpoint for a specific tour spot or festival beyond search results — but agents can work around these.