Korean Government Documents (HWPX)
PYPI · KOREAN-REPORT-HWPX
Turns a draft into a Korean government report or press release as HWPX in each ministry's format
Available components
Last scanned (8 hours ago)
Scores higher than 64% of PyPI servers
Category Documents and Files
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to UpstageAI/korean-report-hwpx). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1288 tokens (~214/item across 6 items; 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (17% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 16 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 17 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- 14 Oct 26 49
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 18 Oct 2026 · Analysed pypi/korean-report-hwpx@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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | UpstageAI/korean-report-hwpx |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/UpstageAI/korean-report-hwpx/.github/workflows/publish-pypi.yml@refs/heads/main |
| Rekor log index | 3164793264 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:c4778b38d6493fb413c24ff509ce1b0e44f9ed3f8a86c32066adde0ea292d3f0 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
build_document ~561
구조 JSON을 기관 서식 HWPX로 만든다(외부 전송 없음, 모두 로컬). 구조는 get_writing_guide 규칙대로 사용자 AI가 작성한다. doc_type='report': {title, date, dept, body, appendix} — ministry를 비우면 공통 서식(기관명 칸 비움). doc_type='press_release': {release, distribute, title, subtitles, body, appendix, contact} — ministry 필수. 입력은 정규화(text 앞 기호·대시·공백 제거)하고, 고칠 점을 warnings로 돌려준다 — 있으면 구조를 고쳐 다시 호출한다. logo_path: 기관 로고 그림(선택). slogan_path: 보도자료 슬로건 그림(선택). placeholder_contact: 보도자료 담당자가 없으면 '○○과 / 김○○ / 044-000-0000' 자리표시로 채움. polish: True면 맥 한컴오피스 한글로 실제 줄 배치를 받아 문단별 자간을 다듬음(맥+한글 필요, 수 분 소요). style: 'standard'(기본, 기존 동작) | 'simplified'(간소화 모드 — 항목 번호 자동 부여, 제목 상자 없음, 표 머리 음영 없음, 표 제목 자동 번호, 서술식 허용). export_markdown: True이면 같은 구조로 .md 파일을 HWPX 옆에 함께 저장(GFM 표, 병합 없이, 번호 위계는 #, ##, ###와 번호 텍스트). report_kind: 'standard'(기본, 기존 보고서 서식) | 'internal'(내부 결재 보고서 — 제목 상자 라벨 없음, 쪽 번호 "- n -", 작성일·부서 "'26. 10. 8.(목) / 과·팀명" 형식, 표 머리 음영 없음/회색, □ 글꼴 HY헤드라인M). 돌려주는 값: {hwpx, doc_type, 문서종류, 기관, warnings, structure(정리된 구조), md(export_markdown=True일 때)}. 같은 이름 .json에 구조도 저장.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | – |
| export_markdown | boolean | – | – |
| logo_path | string | – | – |
| ministry | string | – | – |
| out_path | string | – | – |
| placeholder_contact | boolean | – | – |
| polish | boolean | – | – |
| report_kind | string | – | – |
| slogan_path | string | – | – |
| structure | object | yes | – |
| style | string | – | – |
No output schema declared.
No examples provided.
build_from_structure ~102
build_document와 같다(별칭).
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | – |
| export_markdown | boolean | – | – |
| logo_path | string | – | – |
| ministry | string | – | – |
| out_path | string | – | – |
| placeholder_contact | boolean | – | – |
| polish | boolean | – | – |
| report_kind | string | – | – |
| slogan_path | string | – | – |
| structure | object | yes | – |
| style | string | – | – |
No output schema declared.
No examples provided.
check_structure ~148
구조 JSON을 만들기 전에 점검만 한다(파일 생성 없음): 필수 필드, 알 수 없는 블록, text 속 기호, 계층 건너뜀, □ 두 문장 이상, 보고서 명사형 종결이 아닌 문장, 긴 제목 등. 돌려주는 값: {ok, doc_type, warnings}. style: 'standard'(기본) | 'simplified'(간소화 모드 — 번호 수준 건너뜀, 표 제목 누락, 병합 사용, 5단계 초과 추가 점검).
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | – |
| structure | object | yes | – |
| style | string | – | – |
No output schema declared.
No examples provided.
get_rules ~91
기관·문서 종류별 서식 규칙값: 계층별 기호·기호 앞 공백·글꼴·크기·줄 간격, 계층 사이 빈 줄 크기, 보고서는 제목 상자·표 머리 규칙 포함. ministry를 비우면 보고서 공통 규칙.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | – |
| ministry | string | – | – |
No output schema declared.
No examples provided.
get_writing_guide ~157
원고를 공문서 구조 JSON으로 바꿀 때 지켜야 할 작성 규칙과 스키마·예시. build_document 전에 먼저 확인한다. doc_type: 'report'(보고서) | 'press_release'(보도자료) | 'auto'(둘 다 + 판단 기준). ministry: 기관 이름(선택). style: 'standard'(기본, 기존 동작) | 'simplified'(간소화 모드 — 항목 번호 자동 부여, 제목 상자 없음, 표 머리 음영 없음, 표 제목 자동 번호, 서술식 허용).
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | – |
| ministry | string | – | – |
| style | string | – | – |
No output schema declared.
No examples provided.
list_ministries ~68
지원 기관과 문서 종류별 지원 여부. 보고서: 기관 규칙(42곳) 또는 공통 규칙, 보도자료: 52개 기관. 보고서는 기관을 비우거나 '공통'으로 하면 기관 간 공통 서식으로 만든다.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the Korean Government Documents (HWPX) MCP server?
Korean Government Documents (HWPX) runs locally as a PyPI package, launched with uvx korean-report-hwpx. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · korean-report-hwpx
claude mcp add upstageai-korean-report-hwpx -- uvx korean-report-hwpx
What is the Korean Government Documents (HWPX) MCP server?
Korean Government Documents (HWPX) is an MCP server listed in the public MCP registry as io.github.UpstageAI/korean-report-hwpx. Turns a draft into a Korean government report or press release as HWPX in each ministry's format. This page covers its PyPI package (korean-report-hwpx).
Is the Korean Government Documents (HWPX) MCP server safe to use?
Korean Government Documents (HWPX) scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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 Korean Government Documents (HWPX) MCP server expose?
Korean Government Documents (HWPX) exposes 6 tools: get_writing_guide, check_structure, list_ministries, get_rules, build_document, build_from_structure. Their descriptions and schemas cost roughly 1,127 tokens of context every time the server is loaded.
Is the Korean Government Documents (HWPX) MCP server still maintained?
Korean Government Documents (HWPX) is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Korean Government Documents (HWPX) MCP server under?
Korean Government Documents (HWPX) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.