mcp-server-fooddata-dk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_TOKEN | No | Bearer token required when using the optional HTTP server via /mcp endpoint. | |
| OFF_USER_AGENT | No | A descriptive User-Agent for Open Food Facts API requests. Defaults to this project's name and URL. Set to include a real contact address when running at volume. |
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 |
|---|---|
| fooddata_search_capabilitiesA | Find the right food-data tool. Use first if unsure what is available. |
| fooddata_searchA | Search Danish food/nutrition data by keyword across Open Food Facts (branded/supermarket products) and DTU Frida (generic Danish foods like rugbrød or leverpostej). Returns per-100g calories and macros with source attribution. Use this to get real Danish nutrition values before logging a meal elsewhere. |
| fooddata_get_by_barcodeA | Look up a packaged product by its barcode (EAN) in Open Food Facts. Danish barcode coverage is good but incomplete — if nothing is found, fall back to fooddata_search by name. |
| fooddata_get_foodA | Full detail for a single food by the id returned from fooddata_search ("off:" or "frida:"). |
| fooddata_sourcesA | Which data sources this server has available, and the attribution their licences require. |
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
Tools are largely distinct: search, barcode lookup, ID detail, and meta-info. fooddata_search_capabilities and fooddata_sources both provide meta-info but one guides tool selection while the other covers data sources/licensing. Search vs get_by_barcode is clarified by description, so only minor ambiguity remains.
All tools share the fooddata_ prefix, and most follow a verb_noun pattern (search_capabilities, get_food, get_by_barcode). However, 'fooddata_sources' is a bare noun and 'fooddata_search' is a bare verb, deviating slightly from the consistent verb_noun style.
Five tools is well-scoped for a food data server. Each serves a distinct need: search, barcode lookup, detail retrieval, and source/capability info. No redundant or missing tools for the server's read-only purpose.
The tool surface covers all core operations for a food data lookup server: keyword search, barcode lookup, full detail by ID, and attribution info. There are no dead ends—get_food relies on search IDs, but that is a documented flow. No obvious gaps.