Seoul Data
NPM · @PIPEWORX/MCP-SEOUL-DATA · 2 COMPONENTS
Seoul Open Data MCP — city data for Seoul via the Seoul Open Data Plaza API (openapi.seoul.go.kr).…
Available components
Last scanned (3 hours ago)
Scores higher than 81% of npm servers
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-seoul-data). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 648 tokens (~162/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-seoul-data@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-seoul-data |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-seoul-data/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692346225 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:15f33b5ecc9e0a9157054efc6c1b10239e1292b393bc96c802600d9b06b4fe8500c1d0830ae680df561813099372fe5e6121814a9d674b5accd7096f3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
seoul_air_quality ~85
Real-time air quality across Seoul districts (자치구) — PM10, PM2.5, ozone, NO2, CO, SO2, the comprehensive air index (CAI), and its grade (좋음/Good … 나쁨/Bad). Use for "air quality in Seoul / <district>", "Seoul PM2.5 right now".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seoul_dataset ~161
Generic passthrough to ANY Seoul Open Data Plaza service by its service name (서비스명) — returns the raw rows. Use when a specific Seoul dataset is needed that the named tools don't cover (e.g. "CardSubwayStatsNew" subway ridership, "GetParkingInfo" parking, "tbCycleStationInfo" bike stations, "SPOP_LOCAL_RESD_DONG" population). Browse services at data.seoul.go.kr.
| Name | Type | Req | Description |
|---|---|---|---|
| end | number | – | End row (default 5; sample key caps at 5). |
| service | string | yes | Seoul Open Data service name, e.g. "GetParkingInfo", "tbCycleStationInfo". |
| start | number | – | Start row (1-based, default 1). |
No output schema declared.
No examples provided.
seoul_events ~86
Seoul cultural events — exhibitions, concerts, festivals, performances — with title, category, district, date, venue, target audience, and fee. Use for "cultural events in Seoul", "what's on in <Seoul district>".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max events (default 5; sample key caps at 5, real key up to 1000). |
No output schema declared.
No examples provided.
seoul_real_estate ~262
Seoul property/apartment SALE transactions (실거래가) from the official registry. PREFER for "apartment prices in <Seoul district>", "recent Seoul real-estate sales", "what did <building> sell for". Optionally filter by year and district code. Returns building name, neighborhood (dong), sale price (KRW), floor area (m²), floor, and contract date. Common district codes: 11680=Gangnam, 11650=Seocho, 11710=Songpa, 11110=Jongno, 11140=Jung, 11170=Yongsan, 11440=Mapo, 11200=Seongdong, 11560=Yeongdeungpo, 11620=Gwanak, 11590=Dongjak, 11350=Nowon.
| Name | Type | Req | Description |
|---|---|---|---|
| district_code | string | – | 5-digit Seoul district code, e.g. "11680" (Gangnam) (optional). |
| limit | number | – | Max transactions (default 5; sample key caps at 5, real key up to 1000). |
| year | number | – | Contract year, e.g. 2026 (optional). |
No output schema declared.
No examples provided.
How do I install the Seoul Data MCP server?
Seoul Data runs locally as an npm package, launched with npx -y @pipeworx/mcp-seoul-data. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-seoul-data
claude mcp add pipeworx-io-seoul-data -- npx -y @pipeworx/mcp-seoul-data
What is the Seoul Data MCP server?
Seoul Data is an MCP server listed in the public MCP registry as io.github.pipeworx-io/seoul-data. Seoul Open Data MCP, city data for Seoul via the Seoul Open Data Plaza API (openapi.seoul.go.kr).… This page covers its npm package (@pipeworx/mcp-seoul-data).
Is the Seoul Data MCP server safe to use?
Seoul Data scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Seoul Data MCP server expose?
Seoul Data exposes 4 tools: seoul_real_estate, seoul_air_quality, seoul_events, seoul_dataset. Their descriptions and schemas cost roughly 594 tokens of context every time the server is loaded.
Is the Seoul Data MCP server still maintained?
Seoul Data is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Seoul Data MCP server under?
Seoul Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Seoul Data MCP server?
VerifyMCP ran 16 checks on Seoul Data, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.