Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Korean Public Data

REMOTE · KOREAN-PUBLIC-DATA-MCP.ONRENDER.COM · SCANNED OCT 10

Korean government open data - weather, population, law search via data.go.kr

−57 this week 18 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Korean Public Data MCP server?

Korean Public Data is a hosted endpoint at https://korean-public-data-mcp.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · korean-public-data-mcp.onrender.com

# add to Claude Code
claude mcp add --transport http songt-50-korean-public-data-mcp 'https://korean-public-data-mcp.onrender.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "songt-50-korean-public-data-mcp": {
      "url": "https://korean-public-data-mcp.onrender.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "songt-50-korean-public-data-mcp": {
      "type": "http",
      "url": "https://korean-public-data-mcp.onrender.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.songt-50-korean-public-data-mcp]
url = "https://korean-public-data-mcp.onrender.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "songt-50-korean-public-data-mcp": {
      "type": "remote",
      "url": "https://korean-public-data-mcp.onrender.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add songt-50-korean-public-data-mcp --url 'https://korean-public-data-mcp.onrender.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  songt-50-korean-public-data-mcp:
    url: "https://korean-public-data-mcp.onrender.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "songt-50-korean-public-data-mcp": {
      "Transport": "http",
      "Url": "https://korean-public-data-mcp.onrender.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add songt-50-korean-public-data-mcp -t streamable-http -u 'https://korean-public-data-mcp.onrender.com/mcp'
// mcp.json
{
  "mcpServers": {
    "songt-50-korean-public-data-mcp": {
      "type": "http",
      "url": "https://korean-public-data-mcp.onrender.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 10 Oct 26 −57
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HTTPS: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Oct 26 +57
    • HTTPS: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 28 Sept 26 −5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Sept 26 −41
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.23 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 8 Sept 26 −11
    • Stability: pass → 0.23 functional
  • 1 Sept 26 0
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Destructive annotations: pass functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 10 Oct 2026 · Probed https://korean-public-data-mcp.onrender.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 6eb1e3fe7d0631ea1337bfa4a321c137
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of korean-public-data-mcp.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://korean-public-data-mcp.onrender.com/mcp HTTP error 503
http (plaintext) http://korean-public-data-mcp.onrender.com/mcp Inconclusive 429
MCP tools · 6 exposed · ~635 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_business_registration ~95

사업자등록번호로 사업 상태를 조회합니다. Args: business_numbers: 사업자등록번호 리스트 (예: ["1234567890", "0987654321"]). 하이픈 없이 10자리 숫자. 최대 100개. Returns: 각 사업자의 등록 상태 (계속사업자, 휴업자, 폐업자 등)

NameTypeReqDescription
business_numbersarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_air_quality ~112

실시간 대기질(미세먼지, 초미세먼지, 오존 등)을 조회합니다. Args: location: 지역명 (예: "서울", "강남", "부산", "제주"). 15개 주요 지역 지원. Returns: PM10, PM2.5, 오존, 이산화질소, 일산화탄소, 아황산가스 수치와 등급

NameTypeReqDescription
locationstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_economic_stats ~133

한국은행 경제통계를 조회합니다. Args: indicator: 경제지표명. 지원 항목: 기준금리, 소비자물가지수, 실업률, GDP성장률, 수출액, 수입액, 원달러환율, 코스피 period: 조회기간. "latest"(최근 12개월), "2025"(특정연도), "202501-202602"(기간지정) Returns: 해당 경제지표의 시계열 데이터

NameTypeReqDescription
indicatorstringyes–
periodstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_real_estate_trades ~134

아파트 실거래가를 조회합니다. Args: district: 지역구 이름 (예: "강남구", "서초구", "성남시분당구"). 서울 25개구 + 주요 경기/광역시 지원. year_month: 조회할 연월 (예: "202602"). YYYYMM 형식. Returns: 해당 지역/기간의 아파트 실거래 내역 (단지명, 면적, 가격, 층, 거래일)

NameTypeReqDescription
districtstringyes–
year_monthstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_weather_forecast ~121

도시별 단기 날씨 예보를 조회합니다. Args: city: 도시 이름 (예: "서울", "부산", "제주", "수원"). 25개 주요 도시 지원. hours_ahead: 앞으로 몇 시간 예보를 볼지 (기본 24시간, 최대 72시간) Returns: 시간대별 기온, 강수확률, 하늘상태 등 날씨 정보

NameTypeReqDescription
citystringyes–
hours_aheadinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_supported_options ~40

이 MCP 서버에서 지원하는 도시, 지역, 경제지표 목록을 확인합니다. Returns: 각 도구별 지원 옵션 목록

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the Korean Public Data MCP server?

Korean Public Data is an MCP server listed in the public MCP registry as io.github.SongT-50/korean-public-data-mcp. Korean government open data - weather, population, law search via data.go.kr. This page covers its hosted endpoint (https://korean-public-data-mcp.onrender.com/mcp).

Is the Korean Public Data MCP server safe to use?

Korean Public Data scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Korean Public Data MCP server expose?

Korean Public Data exposes 6 tools: check_business_registration, get_real_estate_trades, get_weather_forecast, get_air_quality, get_economic_stats, list_supported_options. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.

Does the Korean Public Data MCP server require authentication?

Its publisher declares no required credentials for Korean Public Data. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Korean Public Data MCP server still maintained?

Korean Public Data is still listed as active in the MCP registry. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.