Korea Data Suite

Name: Korea Data Suite
Author: choiyounggi

作者：choiyounggi版本 0.1.1i★ –i在你的电脑上运行

注册名称io.github.choiyounggi/korea-data-mcp

安装

概览

作者提供的说明（英文原文）

Korean public holidays, business-day math, and MOLIT real-estate transactions as MCP tools.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 18/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：KDS_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： KDS_API_KEY, KDS_API_BASE

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "korea-data": {
      "command": "uvx",
      "args": [
        "korea-data-mcp"
      ],
      "env": {
        "KDS_API_KEY": "your-value",
        "KDS_API_BASE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add korea-data --env KDS_API_KEY=your-value --env KDS_API_BASE=your-value -- uvx korea-data-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "korea-data": {
      "command": "uvx",
      "args": [
        "korea-data-mcp"
      ],
      "env": {
        "KDS_API_KEY": "your-value",
        "KDS_API_BASE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "korea-data": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "korea-data-mcp"
      ],
      "env": {
        "KDS_API_KEY": "your-value",
        "KDS_API_BASE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

KDS_API_KEY 机密必填 env
Your Korea Data Suite API key (subscribe on the RapidAPI listing).
KDS_API_BASE env
API origin (default https://api.korea-data.cloud).

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 choiyounggi 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18594 个服务器的 0%
发布到注册中心的时间比此分类中其他 18594 个服务器的 17% 更新
基础检查结果等于或优于此分类中其他 18594 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Korea Data Suite 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：KDS_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.1）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Commonly

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

Commonly

Read Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.

作者：Team-Commonly正在增长↓ 4908/周今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Korea Data Suite

English | 한국어

Clean, developer-friendly REST APIs for Korean public data. Korean government open data is powerful but hard to consume — Korean-only docs, XML responses, legacy auth. This suite normalizes it into simple JSON APIs.

▶ [Try it on RapidAPI](https://rapidapi.com/dch0202/api/korea-real-estate-holidays) — free tier, no setup. Hosted and auto-updated; same code as this repo. For AI agents, it's on the MCP Registry — uvx korea-data-mcp.

APIs

API	Status	Description
Holidays & Business Days	✅ v1	Korean public holidays (incl. substitute & temporary holidays) and business-day calculations
Real Estate Transactions	✅ v1	Normalized MOLIT real transaction prices (apartment/officetel/land, sale & rent) — nationwide (261 sigungu)
Address Toolkit	🚧 planned	Road/lot address conversion, romanization
Business Registration	🚧 planned	BRN validation & enrichment

Get started

Hosted (recommended) — a maintained instance with a free tier and no setup:

→ [Subscribe on RapidAPI](https://rapidapi.com/dch0202/api/korea-real-estate-holidays), grab your key, and call any endpoint. RapidAPI injects the key for you — copy a ready-made snippet from its Code Snippets panel.

	RapidAPI (hosted)	Self-host
Setup	API key in seconds	data.go.kr key + server + cron
Data refresh	automatic (we run the sync)	you manage the scheduler
Cost	free tier, then paid	free (your own infra)

Both run the exact same code (this repo). Pick RapidAPI if you'd rather not operate data pipelines; self-host if you want full control.

Self-host

uv sync

uv run uvicorn app.main:app --port 8642 curl "http://127.0.0.1:8642/v1/health"

Holidays & Business Days API

# All holidays in a year (or a month)

curl "http://127.0.0.1:8642/v1/holidays?year=2026" -H "X-API-Key: "

Is a given date a holiday / business day?

curl "http://127.0.0.1:8642/v1/holidays/check?date=2026-03-02" -H "X-API-Key: "

Add N business days (skips weekends & holidays)

curl "http://127.0.0.1:8642/v1/business-days/add?date=2026-12-31&days=1" -H "X-API-Key: "

Count business days in a range (inclusive)

curl "http://127.0.0.1:8642/v1/business-days/count?start=2026-09-21&end=2026-09-27" -H "X-API-Key: "

Covers official public holidays, substitute holidays (대체공휴일), temporary holidays (임시공휴일), and election days — the cases most global holiday APIs get wrong for Korea.

Real Estate Transactions API

Normalized MOLIT (Ministry of Land) real transaction prices — apartment, officetel, and land; sale, jeonse, and monthly-rent — as clean English JSON with cursor pagination.

# Real transaction prices (apartment sales in Gangnam-gu)

curl "http://127.0.0.1:8642/v1/realestate/transactions?region=11680&property_type=apartment&trade_type=sale" -H "X-API-Key: "

Filter by date range + paginate with the returned cursor

curl "http://127.0.0.1:8642/v1/realestate/transactions?region=11680&date_from=2026-01-01&limit=50&cursor= " -H "X-API-Key: "

Region codes (LAWD 5-digit)

curl "http://127.0.0.1:8642/v1/realestate/regions" -H "X-API-Key: "

Daily sync ingests the current + previous month; use the backfill CLI for history:

uv run python scripts/backfill.py --from 2025-01 --to 2025-12 --regions 11680,11650

Configuration

Environment variables (prefix KDS_, .env supported):

Variable	Default	Description
`KDS_DEV_MODE`	`false`	Skip API-key auth (local dev)
`KDS_API_KEYS`	—	Comma-separated accepted API keys
`KDS_PROXY_SECRETS`	—	Comma-separated marketplace proxy secrets
`KDS_DB_PATH`	`data/kds.db`	SQLite path
`KDS_DATA_GO_KR_KEY`	—	data.go.kr service key (optional; enables holiday + real-estate sync)
`KDS_ENABLE_SCHEDULER`	`true`	Holiday (weekly) + real-estate (daily) sync scheduler
`KDS_RE_REGIONS`	all 261 nationwide sigungu	Comma LAWD codes to sync (subset override)
`KDS_RE_DATASETS`	all	Comma dataset keys (apt_trade, apt_rent, offi_trade, offi_rent, land_trade)

Data sources & attribution

Holiday data: KASI Special Day Information (한국천문연구원 특일정보), via Korea Public Data Portal (data.go.kr) — KOGL Type 1. Ships with bundled seed data (2025–2027); refreshed weekly when a service key is configured.
Real transaction data: MOLIT 실거래가 공개시스템 (국토교통부), via Korea Public Data Portal (data.go.kr) — KOGL Type 1.

Run as a daemon (macOS)

# Install & start (auto-restart on crash, start at login)

./scripts/install-daemon.sh

With Cloudflare Tunnel (after one-time `cloudflared tunnel login/create`)

./scripts/install-daemon.sh --with-tunnel

Logs

tail -f ~/Library/Logs/kds/api.out.log

Uninstall

launchctl bootout "gui/$(id -u)" ~/Library/LaunchAgents/com.choiyounggi.kds-api.plist rm ~/Library/LaunchAgents/com.choiyounggi.kds-api.plist

To keep the machine awake for serving, disable system sleep (sudo pmset -a sleep 0) or use a dedicated always-on machine. See deploy/cloudflared.example.yml for exposing the API via Cloudflare Tunnel without opening ports.

Handling concurrent traffic

The read path and the write path are separated so traffic scales independently:

SQLite in WAL mode (set once at init) + busy_timeout — readers never block the daily writer and vice-versa, and multiple read workers can run concurrently.
API process is read-only, multi-worker. scripts/run.sh runs uvicorn with --workers ${KDS_WORKERS:-2} and KDS_ENABLE_SCHEDULER=false. Each worker is a separate process (separate GIL); WAL lets them all read at once. Raise KDS_WORKERS to scale reads with cores.
The daily ingest runs as its own process (com.choiyounggi.kds-sync, 04:00) via scripts/sync.py — never inside the API server, so a multi-thousand-row batch never competes with request handling for the GIL.
Edge caching (optional): responses carry Cache-Control: no-store for security. The real-estate data is public and changes at most daily — if origin load grows, serve it with a short Cache-Control: public, max-age=... and let the CDN absorb reads.

Security checklist before exposing externally

The app is hardened at the code layer (API-key auth fail-closed, parameterized SQL, strict input validation, security headers on every response including 5xx, docs/schema off by default, sanitized errors). The following are edge/deploy responsibilities that must be in place before opening the tunnel:

Never set `KDS_DEV_MODE=true` in production — it disables all auth. The app logs a warning at startup if it is on.
Cloudflare rate limiting + WAF on the tunnel hostname — the app has no app-layer rate limit by design (edge responsibility).
HSTS + TLS are terminated at the Cloudflare edge; confirm HSTS is enabled there (the origin serves plain HTTP on 127.0.0.1 only).
Keep KDS_ENABLE_DOCS unset (or false) in production; set true only to serve /docs /openapi.json at the origin.

SEO marketing site (programmatic)

A static, SEO-optimized marketing site is generated from the live DB by scripts/gen_site.py. For every region that has real transaction data it emits a Korean landing page (the query users actually type — "강남구 아파트 실거래가 API" — backed by real MOLIT stats, a working curl example, and a signup CTA), plus a holidays pillar page, a home page, sitemap.xml, and robots.txt.

Quality gate (important): a region is only published if it has at least MIN_SALE_ROWS (30) apartment-sale rows. Regions without enough data are skipped — this deliberately avoids thin/doorway pages, which search engines penalize.

# generate into site/dist (reads data/kds.db)

uv run python scripts/gen_site.py --out site/dist

Config is env-driven so the same generator works for any domain (put these in deploy/site.env, gitignored — copy deploy/site.env.example):

Env	Meaning
`KDS_SITE_URL`	canonical/sitemap base, e.g. `https://korea-data.cloud`
`KDS_API_ORIGIN`	origin shown in the on-page `curl` examples, e.g. `https://api.korea-data.cloud`
`KDS_CTA_URL`	signup call-to-action (RapidAPI / Zyla / Postman listing)
`KDS_SITE_DIR`	output dir the app serves (default `site/dist`)

Serving — the API app serves it

The FastAPI app serves site/dist at all non-API paths (app.mount("/")), while /v1/* stays the JSON API. The two get different response headers: the API keeps its locked-down default-src 'none' CSP + no-store; the site gets an HTML-renderable CSP (script-src 'none', inline styles allowed) + public cache. Files are read from disk per request, so regenerating the site goes live with no app restart — only a code change needs a restart.

The site is served on the same host as the API (api.korea-data.cloud) — the API lives under /v1, the site everywhere else — so no new tunnel hostname or DNS is needed. One-time on the serving host:

cp deploy/site.env.example deploy/site.env    # KDS_SITE_URL == KDS_API_ORIGIN == https://api.korea-data.cloud

uv run python scripts/gen_site.py --out site/dist # generate once

restart the API app so this integration (new code) takes effect — the site is

then live at https://api.korea-data.cloud/ , /holidays/ , /realestate/... .

Submit https://api.korea-data.cloud/sitemap.xml once in Google Search Console.

Want the site on a bare korea-data.cloud / www later? Add an ingress rule

pointing that hostname at the same http://127.0.0.1:8642, route its DNS, and

switch KDS_SITE_URL to it. Not required — the api host works for SEO today.

First run needs history: the daily sync only ingests the current month. To give

pages real depth, backfill once —

uv run python scripts/backfill.py --from 2025-07 --to 2026-06 --regions --datasets apt_trade,apt_rent.

Automate (macOS daemon)

deploy/com.choiyounggi.kds-site.plist regenerates the site daily at 04:30 (right after the 04:00 sync) via scripts/publish_site.sh. Because the app serves from disk, the refreshed pages are live immediately — no restart, no external deploy:

cp deploy/com.choiyounggi.kds-site.plist ~/Library/LaunchAgents/

launchctl bootstrap "gui/$(id -u)" ~/Library/LaunchAgents/com.choiyounggi.kds-site.plist tail -f ~/Library/Logs/kds/site.out.log

Uptime note: since the site is served by the local app (not a CDN), its SEO

availability tracks the machine — keep it awake for serving (pmset, as the API

already requires). If always-on hosting is wanted later, the same site/dist can

be pushed to Cloudflare Pages instead.

MCP server (AI-agent access)

The API is also packaged as a standalone Model Context Protocol server — packages/korea-data-mcp/ — so AI agents (Claude Desktop/Code, Cursor, …) can discover and call the endpoints directly. It is its own minimal package (deps: mcp, httpx) and is what gets published to PyPI / listed in the MCP Registry.

Quick add (before PyPI, straight from this repo — users bring their own key):

claude mcp add korea-data-suite --env KDS_API_KEY=<key> \

-- uvx --from "git+https://github.com/choiyounggi/korea-data-suite#subdirectory=packages/korea-data-mcp" korea-data-mcp

See packages/korea-data-mcp/README.md for tools, client config, and uvx korea-data-mcp (once on PyPI).

Korea Data Suite

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

Commonly

作者的 README

Korea Data Suite

APIs

Get started

Self-host

Holidays & Business Days API

Is a given date a holiday / business day?

Add N business days (skips weekends & holidays)

Count business days in a range (inclusive)

Real Estate Transactions API

Filter by date range + paginate with the returned cursor

Region codes (LAWD 5-digit)

Configuration

Data sources & attribution

Run as a daemon (macOS)

With Cloudflare Tunnel (after one-time cloudflared tunnel login/create)

Logs

Uninstall

Handling concurrent traffic

Security checklist before exposing externally

SEO marketing site (programmatic)

Serving — the API app serves it

restart the API app so this integration (new code) takes effect — the site is

then live at https://api.korea-data.cloud/ , /holidays/ , /realestate/... .

Automate (macOS daemon)

MCP server (AI-agent access)

License

With Cloudflare Tunnel (after one-time `cloudflared tunnel login/create`)