accueil / serveurs / Recherche & Web / io.github.cyanheads/usda-mcp-server
io.github.cyanheads/usda-mcp-server
serveur MCP (Model Context Protocol) · usda-mcp-server 0.1.11
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.cyanheads/usda-mcp-server est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/usda-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- usda_compare_foods≈ 1428 tokens
Compare nutrients side-by-side for 2–5 foods. Returns a structured table — one row per nutrient, one column per food — formatted as markdown. Best for "spinach vs kale iron" or "which has more protein?" questions. Omit nutrients[] to use the 12 most common defaults (energy, protein, fat, saturated fat, carbs, fiber, sugars, sodium, potassium, calcium, iron, vitamin C); provide nutrients[] with specific FDC IDs to compare different nutrients. All values are scaled to the same gram basis (default 100g). If one or more FDC IDs are not found, the comparison proceeds with the valid foods — only throws too_few_foods when fewer than 2 IDs return data.
Paramètres, retour & exemple (4)
Paramètresunit· string · optionnel · g | oz | lb | kg
Unit for quantity. Default "g". Does not support "serving" (use a fixed gram basis for consistent comparison).fdcIds· array · requis
FDC IDs to compare — 2 to 5 foods. Use usda_search_foods to discover IDs.quantity· number · optionnel
Gram basis for comparison. All values scaled to this amount. Must be positive. Default 100.nutrients· array · optionnel
Nutrient IDs to include in the comparison. Defaults to the 12 most common: energy (1008), protein (1003), total fat (1004), saturated fat (1258), carbohydrate (1005), fiber (1079), total sugars (2000), sodium (1093), potassium (1092), calcium (1087), iron (1089), vitamin C (1162). Use usda_list_nutrients to look up other IDs.
Exemple d'appel{"name": "usda_compare_foods", "arguments": {"fdcIds": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"basis": {}, "error": {}, "foods": [], "nutrients": [], "missingData": []}} - usda_get_food≈ 1562 tokens
Get the full nutrient profile for one food by FDC ID. Returns all available nutrients (or a filtered subset via the nutrients[] param) with optional per-portion scaling. Use usda_search_foods to discover FDC IDs. Provide quantity + unit to scale all nutrient values from per-100g to the specified portion (e.g. quantity=200, unit="g" → per-200g values). Use unit="serving" to scale to the food's first defined portion weight. Narrow nutrients[] to specific IDs to reduce response size for focused queries.
Paramètres, retour & exemple (4)
Paramètresunit· string · optionnel · g | oz | lb | kg | serving
Unit for quantity. "serving" uses the food's first defined portion weight. Required when quantity is provided.fdcId· integer · requis
FDC ID of the food. Use usda_search_foods to discover IDs.quantity· number · optionnel
Amount of food to scale nutrient values to. Must be positive. When provided, unit is required. Omit for per-100g values (FDC database native basis).nutrients· array · optionnel
Filter to specific nutrient IDs (e.g. [1003, 1004, 1005, 1008] for protein, fat, carbs, energy). Use usda_list_nutrients to look up IDs. Omit to return all available nutrients.
Exemple d'appel{"name": "usda_get_food", "arguments": {"fdcId": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "fdcId": 1, "dataType": "texte", "scaledTo": {}, "brandName": "texte", "nutrients": [], "brandOwner": "texte", "allPortions": [], "description": "texte", "ingredients": "texte", "servingInfo": {}, "foodCategory": "texte"}} - usda_get_foods≈ 1016 tokens
Fetch nutrient profiles for 2–20 foods in a single API call. More efficient than calling usda_get_food N times when you already have multiple FDC IDs. All values are per 100g (no portion scaling). Use the nutrients[] filter to limit response size — strongly recommended for batch calls. For side-by-side comparison with a formatted table, use usda_compare_foods instead. Failed IDs (not found or no data) are reported in the failed[] array rather than aborting the entire batch.
Paramètres, retour & exemple (2)
ParamètresfdcIds· array · requis
FDC IDs to fetch — 2 to 20 IDs. Use usda_search_foods to discover IDs.nutrients· array · optionnel
Filter to specific nutrient IDs (e.g. [1003, 1004, 1005, 1008]). Strongly recommended — full profiles can be large. Use usda_list_nutrients to look up IDs.
Exemple d'appel{"name": "usda_get_foods", "arguments": {"fdcIds": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "foods": [], "failed": []}} - usda_list_nutrients≈ 730 tokens
Look up the FDC nutrient reference table — all tracked nutrients with their numeric IDs, names, SR reference numbers, units, and categories. Use to resolve a nutrient name (e.g. "vitamin C") to its FDC ID (1162) before passing it to the nutrients[] filter on other tools. Filter by category (macronutrients, vitamins, minerals, lipids, amino_acids, or other) to narrow results. The data is static — call once and reuse the IDs.
Paramètres, retour & exemple (1)
Paramètrescategory· string · optionnel · macronutrients | vitamins | minerals | lipids | amino_acids | other
Filter to a nutrient category. Omit to return all ~150 tracked nutrients. Options: macronutrients, vitamins, minerals, lipids, amino_acids, other.
Exemple d'appel{"name": "usda_list_nutrients", "arguments": {"category": "macronutrients"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "nutrients": []}} - usda_search_foods≈ 1532 tokens
Search USDA FoodData Central foods by keyword. Returns matching foods with FDC IDs and a preview of key nutrients (energy, protein, fat, carbs — not guaranteed complete). Use the returned fdcId with usda_get_food for the full nutrient profile, or usda_compare_foods for side-by-side comparisons. When dataType is omitted, defaults to SR Legacy (common whole foods with complete profiles) — or to Branded when brandOwner is set, since only Branded records carry one. Set dataType to ["Branded"] for packaged products, or include a UPC/GTIN code as the query. Pass brandOwner (e.g. "General Mills") to narrow branded results.
Paramètres, retour & exemple (6)
Paramètresquery· string · requis
Search terms — food name, ingredient, or UPC/GTIN code for branded products. Examples: "chicken breast raw", "banana", "012345678901".dataType· array · optionnel
FDC data sources to search. Omitting this defaults to ["SR Legacy"] (common whole foods, complete nutrient profiles), or to ["Branded"] when brandOwner is set. Include "Branded" for packaged products. Multiple values allowed.pageSize· integer · optionnel
Number of results per page. Default 10, maximum 50.brandOwner· string · optionnel
Filter branded results by brand owner name (e.g. "General Mills", "Kraft"). Only Branded records carry one, so setting this defaults dataType to ["Branded"] unless dataType is given explicitly.pageNumber· integer · optionnel
Page number (1-based). Use with totalPages to paginate.foodCategory· string · optionnel
Filter by USDA food category (e.g. "Poultry Products", "Vegetables and Vegetable Products"). Case-sensitive.
Exemple d'appel{"name": "usda_search_foods", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "foods": [], "totalHits": 1, "totalCount": 1, "totalPages": 1, "currentPage": 1}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».