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.

io.github.wujinkim/korea-business-verify

NPM · KOREA-BUSINESS-VERIFY · SCANNED SEP 22

한국 사업자 검증 액션 MCP 서버 — 진위확인·휴폐업·과세유형·세금계산서 발행 가능 여부 (국세청 공공데이터 기반)

0 this week 83 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 323 tokens (~64/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 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
Install

How do I install the io.github.wujinkim/korea-business-verify MCP server?

io.github.wujinkim/korea-business-verify runs locally as an npm package, launched with npx -y korea-business-verify. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · korea-business-verify

# add to Claude Code
claude mcp add wujinkim-korea-business-verify -- npx -y korea-business-verify
// .cursor/mcp.json
{
  "mcpServers": {
    "wujinkim-korea-business-verify": {
      "command": "npx",
      "args": [
        "-y",
        "korea-business-verify"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wujinkim-korea-business-verify": {
      "command": "npx",
      "args": [
        "-y",
        "korea-business-verify"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add wujinkim-korea-business-verify -- npx -y korea-business-verify
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wujinkim-korea-business-verify": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "korea-business-verify"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add wujinkim-korea-business-verify --command npx --arg -y --arg korea-business-verify
# ~/.hermes/config.yaml
mcp_servers:
  wujinkim-korea-business-verify:
    command: "npx"
    args: ["-y", "korea-business-verify"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wujinkim-korea-business-verify": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "korea-business-verify"
      ]
    }
  }
}
# add to Vellum
assistant mcp add wujinkim-korea-business-verify -t stdio -c npx -a -y korea-business-verify
// mcp.json
{
  "mcpServers": {
    "wujinkim-korea-business-verify": {
      "command": "npx",
      "args": [
        "-y",
        "korea-business-verify"
      ]
    }
  }
}
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.

  • 22 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 21 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 16 Sept 26 −2
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

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 22 Sept 2026 · Analysed npm/korea-business-verify@0.1.1

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 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~323 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
batch_check_status ~49

최대 100건 사업자 상태 일괄 조회. 경비처리·정산 자동화용.

NameTypeReqDescription
business_numbersarrayyes사업자번호 목록 (최대 100)

No output schema declared.

No examples provided.

check_business_status ~47

사업자 휴폐업 상태·과세유형·폐업일자 조회. 호출 빈도가 가장 높은 도구.

NameTypeReqDescription
business_nostringyes사업자등록번호

No output schema declared.

No examples provided.

check_invoice_eligibility ~63

과세유형·휴폐업 상태를 종합해 세금계산서 수취 가능 여부 판정 + 근거. 순수 래퍼 대비 차별화 도구.

NameTypeReqDescription
business_nostringyes사업자등록번호

No output schema declared.

No examples provided.

explain_kr_tax_type ~59

한국 과세유형(일반/간이/면세/비과세)의 실무 의미 해설. API 호출 없음.

NameTypeReqDescription
tax_typestring과세유형 문자열 (생략 시 전체 목록)

No output schema declared.

No examples provided.

verify_business ~105

한국 사업자등록정보 진위확인. 국세청 등록정보와 입력(사업자번호·대표자명·개업일자)의 일치 여부. 대표자명은 검증 즉시 폐기되며 저장되지 않습니다.

NameTypeReqDescription
business_nostringyes사업자등록번호 (하이픈 무관)
opening_datestringyes개업일자 (YYYYMMDD)
representative_namestringyes대표자 성명

No output schema declared.

No examples provided.

Common questions

What is the io.github.wujinkim/korea-business-verify MCP server?

io.github.wujinkim/korea-business-verify is an MCP server listed in the public MCP registry as io.github.wujinkim/korea-business-verify. 한국 사업자 검증 액션 MCP 서버, 진위확인·휴폐업·과세유형·세금계산서 발행 가능 여부 (국세청 공공데이터 기반). This page covers its npm package (korea-business-verify).

Is the io.github.wujinkim/korea-business-verify MCP server safe to use?

io.github.wujinkim/korea-business-verify scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 io.github.wujinkim/korea-business-verify MCP server expose?

io.github.wujinkim/korea-business-verify exposes 5 tools: verify_business, check_business_status, batch_check_status, check_invoice_eligibility, explain_kr_tax_type. Their descriptions and schemas cost roughly 323 tokens of context every time the server is loaded.

Is the io.github.wujinkim/korea-business-verify MCP server still maintained?

io.github.wujinkim/korea-business-verify is still listed as active in the MCP registry. We last reached this channel on 22 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 io.github.wujinkim/korea-business-verify MCP server under?

io.github.wujinkim/korea-business-verify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.