Korean Fire Safety Law & Statistics
NPM · KOREAN-FIREFIGHTER-LAW-MCP · SCANNED SEP 23
Korean fire safety law, statutes, NFPC/NFTC codes, hazmat, and fire/EMS statistics.
Available components
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 Security98
- 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
- 34 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1296 tokens (~117/item across 11 items; 11 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 Management80
- Stability observed for 24 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
How do I install the Korean Fire Safety Law & Statistics MCP server?
Korean Fire Safety Law & Statistics runs locally as an npm package, launched with npx -y korean-firefighter-law-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · korean-firefighter-law-mcp
claude mcp add ssd7830-cmyk-korean-firefighter-law-mcp -- npx -y korean-firefighter-law-mcp
{
"mcpServers": {
"ssd7830-cmyk-korean-firefighter-law-mcp": {
"command": "npx",
"args": [
"-y",
"korean-firefighter-law-mcp"
]
}
}
} {
"servers": {
"ssd7830-cmyk-korean-firefighter-law-mcp": {
"command": "npx",
"args": [
"-y",
"korean-firefighter-law-mcp"
]
}
}
} codex mcp add ssd7830-cmyk-korean-firefighter-law-mcp -- npx -y korean-firefighter-law-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ssd7830-cmyk-korean-firefighter-law-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"korean-firefighter-law-mcp"
],
"enabled": true
}
}
} openclaw mcp add ssd7830-cmyk-korean-firefighter-law-mcp --command npx --arg -y --arg korean-firefighter-law-mcp
mcp_servers:
ssd7830-cmyk-korean-firefighter-law-mcp:
command: "npx"
args: ["-y", "korean-firefighter-law-mcp"] {
"McpServers": {
"ssd7830-cmyk-korean-firefighter-law-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"korean-firefighter-law-mcp"
]
}
}
} assistant mcp add ssd7830-cmyk-korean-firefighter-law-mcp -t stdio -c npx -a -y korean-firefighter-law-mcp
{
"mcpServers": {
"ssd7830-cmyk-korean-firefighter-law-mcp": {
"command": "npx",
"args": [
"-y",
"korean-firefighter-law-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
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 23 Sept 2026 · Analysed npm/korean-firefighter-law-mcp@0.8.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 111 packages
| Packages resolved | 111 |
|---|---|
| Stale | 34 |
| 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 →
get_building_facilities ~99
특정소방대상물의 소방시설 현황 조회 (스프링클러 설치 여부 등)
| Name | Type | Req | Description |
|---|---|---|---|
| buildingName | string | – | 대상물명 (선택, 전체 페이지 결과 내 필터) |
| numOfRows | integer | – | 결과 수 (최대 1000) |
| pageNo | integer | – | 페이지 번호 |
| sido | string | yes | 시도명 (예: 서울특별시) |
No output schema declared.
No examples provided.
get_ems_stats ~174
시도본부·소방서별 구급활동 통계 조회 (교통사고 구급활동: 출동·이송 건수)
| Name | Type | Req | Description |
|---|---|---|---|
| fireStation | string | – | 출동소방서명 (선택) |
| month | string | – | 접수년월 (YYYYMM, 선택) |
| numOfRows | integer | – | 결과 수 (최대 1000) |
| pageNo | integer | – | 페이지 번호 |
| patientType | string | – | 환자유형 (선택) |
| sido | string | yes | 정확한 시도본부명 (예: 서울소방재난본부, 인천소방본부, 대구소방안전본부, 제주특별자치도는 제주소방안전본부) |
No output schema declared.
No examples provided.
get_fire_admin_rule_text ~121
화재안전성능기준(NFPC)·화재안전기술기준(NFTC) 행정규칙 원문 및 절 번호 조회
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | 행정규칙일련번호 (검색 결과의 ID) |
| ruleName | string | – | 행정규칙명 또는 NFPC/NFTC 코드 (id가 없을 때 검색) |
| section | string | – | 찾을 절 번호 또는 키워드 (예: "2.5.3", "공동주택") |
No output schema declared.
No examples provided.
get_fire_law_annex ~119
소방 법령 시행령 등의 별표 원문 조회. 별표 번호와 키워드로 적용 대상·시설 기준 확인
| Name | Type | Req | Description |
|---|---|---|---|
| annex | string | – | 별표 번호 (예: "4", "별표 4") |
| lawName | string | – | 법령명 (약칭 지원, mst 없을 때 검색) |
| mst | string | – | 법령일련번호 MST |
| query | string | – | 별표 안에서 찾을 키워드 (예: "공동주택") |
No output schema declared.
No examples provided.
get_fire_law_text ~159
소방 법령 조문 전문 조회 (예: lawName="소방시설법", jo="제10조")
| Name | Type | Req | Description |
|---|---|---|---|
| jo | string | – | 조번호 (예: "제10조", "10", "10의2"). 비우면 전체 (길면 잘림) |
| lawName | string | – | 법령명 (약칭 지원, mst 없을 때 검색해서 첫 매칭 사용) |
| mst | string | – | 법령일련번호 MST (search_fire_law 결과의 값, 있으면 우선) |
| query | string | – | 조문 내용에서 찾을 키워드 (예: "방화문") — 조번호를 모를 때 관련 조문만 추출 |
No output schema declared.
No examples provided.
search_fire_admin_rules ~125
소방 행정규칙(고시·훈령) 검색 (법제처). 스프링클러·경보설비 등 소방시설 설치 기준의 본체인 화재안전성능기준(NFPC)·화재안전기술기준(NFTC)이 여기 있음
| Name | Type | Req | Description |
|---|---|---|---|
| display | integer | – | 결과 수 |
| query | string | yes | 검색어 — 시설명이면 충분 (예: "스프링클러", "옥내소화전", "자동화재탐지설비") |
No output schema declared.
No examples provided.
search_fire_building ~121
특정소방대상물(건물) 검색 — 시도·건물명·사용승인연도별
| Name | Type | Req | Description |
|---|---|---|---|
| approvalYear | string | – | 사용승인 연도 (YYYY, 선택) |
| buildingName | string | – | 대상물명 (선택, 전체 페이지 결과 내 필터) |
| numOfRows | integer | – | 결과 수 (최대 1000) |
| pageNo | integer | – | 페이지 번호 |
| sido | string | yes | 시도명 (예: 서울특별시, 경기도) |
No output schema declared.
No examples provided.
search_fire_law ~99
소방 관계 법령 검색 (법제처). 약칭 지원: 화재예방법·소방시설법·위험물법 등. 검색어 없으면 소방 법령 목록
| Name | Type | Req | Description |
|---|---|---|---|
| display | integer | – | 결과 수 |
| query | string | – | 법령명 또는 키워드 (약칭 지원: 화재예방법, 소방시설법 등). 비우면 소방 법령 목록 표시 |
No output schema declared.
No examples provided.
search_fire_precedents ~78
소방 관련 판례 검색 (법제처). 소방시설·위험물·소방공무원 관련 재판례
| Name | Type | Req | Description |
|---|---|---|---|
| display | integer | – | 결과 수 |
| query | string | yes | 검색어 (예: 소방시설 점검, 위험물 저장, 소방공무원 순직) |
No output schema declared.
No examples provided.
search_fire_stats ~103
날짜별 화재발생현황 조회 (소방청 국가화재정보). 접수·진행·오인·자체진화 건수 등
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 발생일자 (YYYYMMDD, 예: 20250315) |
| numOfRows | integer | – | 결과 수 (기본·최대 1000, 일자 결과 누락 방지) |
| pageNo | integer | – | 페이지 번호 |
No output schema declared.
No examples provided.
search_hazmat ~98
위험물안전관리법상 위험물 검색 (소방청 국가위험물정보). 물질명·CAS번호·UN번호로 품명(류별)·물성·사용용도 조회
| Name | Type | Req | Description |
|---|---|---|---|
| display | integer | – | 결과 수 |
| query | string | yes | 물질명·CAS번호·UN번호 (예: "아세톤", "67-64-1", "1090") |
No output schema declared.
No examples provided.
What is the Korean Fire Safety Law & Statistics MCP server?
Korean Fire Safety Law & Statistics is an MCP server listed in the public MCP registry as io.github.ssd7830-cmyk/korean-firefighter-law-mcp. Korean fire safety law, statutes, NFPC/NFTC codes, hazmat, and fire/EMS statistics. This page covers its npm package (korean-firefighter-law-mcp).
Is the Korean Fire Safety Law & Statistics MCP server safe to use?
Korean Fire Safety Law & Statistics scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. 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 Fire Safety Law & Statistics MCP server expose?
Korean Fire Safety Law & Statistics exposes 11 tools: search_fire_stats, get_ems_stats, search_fire_building, get_building_facilities, search_fire_law, and 6 more. Their descriptions and schemas cost roughly 1,296 tokens of context every time the server is loaded.
Is the Korean Fire Safety Law & Statistics MCP server still maintained?
Korean Fire Safety Law & Statistics is still listed as active in the MCP registry. We last reached this channel on 23 September 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 Fire Safety Law & Statistics MCP server under?
Korean Fire Safety Law & Statistics declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.