K-MFDS FoodDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOV_API_KEY | Yes | 식품의약품안전처 OpenAPI 키 |
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 |
|---|---|
| searchFoodNutritionC | 식품의약품안전처 식품영양성분DB에서 식품 정보를 검색합니다. 식품명, 제조사, 카테고리 등을 기준으로 검색할 수 있습니다. |
| getNutritionComponentTypesB | 식품영양성분DB에서 제공하는 영양성분 유형 목록을 조회합니다. |
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 2 tools
The two tools have completely distinct purposes: one lists nutrient component types, the other searches for food nutrition data. No overlap or ambiguity.
Both tools follow a consistent verb_noun naming pattern: getNutritionComponentTypes and searchFoodNutrition, using clear prefixes.
With only 2 tools, the server feels very thin for a food nutrition database domain. A typical scope would require at least 4-5 tools for basic CRUD and search.
Missing essential operations like retrieving full nutrition details for a specific food, filtering by nutrient, or adding/updating data. Users can list types and search, but cannot retrieve individual food details.