Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Korean public holidays, business-day math, and MOLIT real-estate transactions as MCP tools.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
KDS_API_KEY, KDS_API_BASEAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"korea-data": {
"command": "uvx",
"args": [
"korea-data-mcp"
],
"env": {
"KDS_API_KEY": "your-value",
"KDS_API_BASE": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add korea-data --env KDS_API_KEY=your-value --env KDS_API_BASE=your-value -- uvx korea-data-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"korea-data": {
"command": "uvx",
"args": [
"korea-data-mcp"
],
"env": {
"KDS_API_KEY": "your-value",
"KDS_API_BASE": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"korea-data": {
"type": "stdio",
"command": "uvx",
"args": [
"korea-data-mcp"
],
"env": {
"KDS_API_KEY": "your-value",
"KDS_API_BASE": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
KDS_API_BASE envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto choiyounggi bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: KDS_API_KEY
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.1) kam vor 3 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Python (uv) auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, ScienceShot science reference
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Sourced, citable answers in radiation and particle physics, photonics, electronics and quantum.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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.
| 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 |
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.
uv sync
uv run uvicorn app.main:app --port 8642 curl "http://127.0.0.1:8642/v1/health"
# All holidays in a year (or a month)
curl "http://127.0.0.1:8642/v1/holidays?year=2026" -H "X-API-Key: "
curl "http://127.0.0.1:8642/v1/holidays/check?date=2026-03-02" -H "X-API-Key: "
curl "http://127.0.0.1:8642/v1/business-days/add?date=2026-12-31&days=1" -H "X-API-Key: "
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.
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: "
curl "http://127.0.0.1:8642/v1/realestate/transactions?region=11680&date_from=2026-01-01&limit=50&cursor= " -H "X-API-Key: "
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
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) |
# Install & start (auto-restart on crash, start at login)
./scripts/install-daemon.sh
cloudflared tunnel login/create)./scripts/install-daemon.sh --with-tunnel
tail -f ~/Library/Logs/kds/api.out.log
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.
The read path and the write path are separated so traffic scales independently:
busy_timeout — readers never block the daily writer and vice-versa, and multiple read workers can run concurrently.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.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.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.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:
127.0.0.1 only).KDS_ENABLE_DOCS unset (or false) in production; set true only to serve /docs /openapi.json at the origin.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) |
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
Submit https://api.korea-data.cloud/sitemap.xml once in Google Search Console.
Want the site on a bare
korea-data.cloud/wwwlater? Add an ingress rule
pointing that hostname at the same
http://127.0.0.1:8642, route its DNS, and
switch
KDS_SITE_URLto 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.
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/distcan
be pushed to Cloudflare Pages instead.
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).
MIT © choiyounggi