korea-business-verify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTS_SERVICE_KEY | No | 국세청 서비스키. 설정하지 않으면 DEMO 모드로 동작합니다. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_businessA | 한국 사업자등록정보 진위확인. 국세청 등록정보와 입력(사업자번호·대표자명·개업일자)의 일치 여부. 대표자명은 검증 즉시 폐기되며 저장되지 않습니다. |
| check_business_statusA | 사업자 휴폐업 상태·과세유형·폐업일자 조회. 호출 빈도가 가장 높은 도구. |
| batch_check_statusA | 최대 100건 사업자 상태 일괄 조회. 경비처리·정산 자동화용. |
| check_invoice_eligibilityB | 과세유형·휴폐업 상태를 종합해 세금계산서 수취 가능 여부 판정 + 근거. 순수 래퍼 대비 차별화 도구. |
| explain_kr_tax_typeA | 한국 과세유형(일반/간이/면세/비과세)의 실무 의미 해설. API 호출 없음. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools are mostly distinct: verify_business checks authenticity, check_business_status and batch_check_status handle single vs bulk status queries, check_invoice_eligibility is a composite assessment, and explain_kr_tax_type is educational. The minor overlap between the two status-check tools is mitigated by clear descriptions.
Most tools follow a verb_noun pattern (verify_business, check_business_status, explain_kr_tax_type), but 'batch_check_status' deviates slightly with an adjective modifier and 'kr' in one name adds minor inconsistency. Overall the convention is clear and predictable.
Five tools is well-scoped for a specialized verification server. Each tool serves a distinct purpose, and the count is neither too thin nor too heavy for the domain.
The core verification workflow is well covered: authenticity checks, status lookup (single and bulk), invoice eligibility, and tax type explanation. Minor gaps exist, such as a dedicated tool for fetching full business registration details, but the main use cases are supported.