Nutriscan MCP connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP listen port when running in HTTP mode. | 3000 |
| USDA_API_KEY | No | USDA FoodData Central API key. If omitted, the shared DEMO_KEY is used. | DEMO_KEY |
| MCP_TRANSPORT | No | Transport mode. Use stdio or http; same as the --http option. | stdio |
| USDA_DAILY_LIMIT | No | Local daily cap for USDA FoodData Central requests. Resets at 00:00 UTC. | 50 with DEMO_KEY, otherwise 100000 |
| NUTRISCAN_CONTACT | No | Contact email sent in the Open Food Facts User-Agent as Nutriscan/0.1 (<contact>). | contact@example.com |
| USDA_HOURLY_LIMIT | No | Local hourly cap for USDA FoodData Central requests. | 30 with DEMO_KEY, otherwise 1000 |
| NUTRISCAN_DATA_DIR | No | Directory for meals.json, relative to the process working directory. | ./data |
| NUTRISCAN_OFF_BASE_URL | No | Base URL for Open Food Facts product and search requests. | https://world.openfoodfacts.org |
| NUTRISCAN_USDA_BASE_URL | No | Base URL for USDA FoodData Central requests. | https://api.nal.usda.gov/fdc/v1 |
| NUTRISCAN_OFF_SEARCH_PER_MINUTE | No | Local per-minute cap on Open Food Facts searches. | 10 |
| NUTRISCAN_OFF_PRODUCT_PER_MINUTE | No | Local per-minute cap on Open Food Facts product reads. | 100 |
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 |
|---|---|
| barcode_lookupA | Look up one packaged food on Open Food Facts by barcode (EAN-8, UPC-A, or EAN-13). Returns name, brand, quantity, Nutri-Score, NOVA group, allergens, additives, and key nutrients per 100 g. Use when the user has a barcode. For a name, use product_search. |
| product_searchA | Search Open Food Facts by food name (full text). Returns a short page of matches with barcode, name, brand, quantity, Nutri-Score, and NOVA group. Optional brand and country filters. Does not return nutrient tables; call barcode_lookup for those. Limited to 10 searches per minute. |
| allergens_additivesA | List allergens, may-contain traces, and additives (E-numbers) for one Open Food Facts product by barcode, plus a short ingredients line. Use for allergy and ingredient questions. |
| nutriscore_novaA | Return the Nutri-Score letter (A best to E worst) and NOVA processing group (1 minimally processed to 4 ultra-processed) for one barcode, each with a one-line meaning. Missing scores are null, not an error. Not medical or dietary advice. |
| nutrients_per_servingA | Energy and key nutrients for one Open Food Facts product, scaled from per-100 g data to one label serving, a number of servings, or a gram amount. Pass grams when the product has no serving size. Salt is in grams. If both grams and servings are set, grams wins. |
| usda_food_searchA | Search USDA FoodData Central for generic or branded foods (no barcode required). Returns fdcId, description, data type, and key nutrients per 100 g, including sodium in milligrams. Uses USDA_API_KEY, or the shared demo key (about 30 requests per hour and 50 per day) when that variable is unset. The key is never included in the result. |
| compare_productsA | Compare two Open Food Facts products by barcode on nutrients per 100 g, Nutri-Score, NOVA, and allergens. barcode_a and barcode_b are returned as a and b. Says which side is numerically lower. A lower number is not always better (protein and fiber are often desirable). Not dietary advice. |
| meal_log_addA | Append one eaten food to the local meal log (a JSON file on disk; nothing is uploaded). Pass a barcode to snapshot Open Food Facts nutrients, plus grams or servings. Without a barcode, pass a name and grams (nutrients are then omitted from totals). Optional meal slot and UTC date (YYYY-MM-DD). |
| meal_log_listA | List entries in the local meal log, newest first. Optional UTC date (YYYY-MM-DD) and limit. Does not call Open Food Facts or USDA. |
| meal_log_day_totalA | Sum energy and key nutrients for one UTC day in the local meal log. Entries logged without nutrients are counted separately and are not added into the totals. Optional date (YYYY-MM-DD), default today UTC. |
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 10 tools
Each tool targets a distinct action/resource, and descriptions explicitly disambiguate the closest pairs (product_search for names vs barcode_lookup for barcodes; barcode_lookup for per-100 g tables vs nutrients_per_serving for scaled values). The only mild overlaps are barcode_lookup vs nutriscore_nova/allergens_additives, which return subsets of the same product data but are clearly scoped by purpose.
All names are snake_case and mostly follow a noun-first-with-verb-suffix pattern (product_search, barcode_lookup, meal_log_add, meal_log_list), with domain prefixes grouping meal_log_* tools nicely. However, compare_products is verb-first while everything else is noun-first, and several tools (nutrients_per_serving, allergens_additives, nutriscore_nova) are noun phrases with no verb at all, so the pattern is readable but not uniform.
Ten tools is well within the ideal range and each one earns its place: three lookup/search entry points, three nutrient-analysis tools, three meal-log tools, and one comparison tool. No obviously redundant or filler tools.
The read side is thorough (name search, barcode lookup, USDA fallback, nutrients, scores, allergens, comparison), and meal logging covers add/list/day-total. But the meal log has no delete, update, or clear operation, so a mistakenly logged entry is a permanent dead end that will skew day totals — a notable lifecycle gap.