kfda-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MFDS_API_KEY | Yes | Your MFDS API key from data.go.kr |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_drugA | 식약처 의약품 마스터에서 약품을 검색합니다 (Korean drug master search). 제품명, 성분명, 제조사 등으로 조회 가능. Returns product_name, generic_name, manufacturer, ATC code, indication. |
| check_dur_interactionB | 식약처 의약품 안전사용서비스(DUR)에서 두 약물의 병용금기·연령금기 등 안전성 정보를 확인합니다. Check Korean Drug Utilization Review (DUR) safety rules between two drugs. |
| search_supplementA | 식약처 식품안전나라 건강기능식품 인허가 정보를 검색합니다. Search Korean functional health food (건기식) registrations by ingredient or product name. |
| get_drug_easy_infoA | 식약처 e약은요 (환자용 쉬운 약물 정보)를 조회합니다. Get patient-friendly Korean drug information: purpose, dosage, side effects, warnings. |
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 4 tools
Each tool has a clearly distinct purpose: interaction checking, patient info retrieval, drug search, and supplement search. There is no overlap or ambiguity among them.
All tool names follow a consistent verb_noun pattern with underscores (e.g., check_dur_interaction, search_drug). The naming is predictable and uniform.
With 4 tools, the server is well-scoped for a focused domain of Korean drug and supplement information. Each tool serves a distinct function without redundancy.
The server covers drug search, patient information, interaction checking, and supplement search—key functionalities. Minor gaps exist (e.g., professional-level drug details), but the core workflows are supported.