kabo-nutrition-mcp
Related Servers
Alternatives to kabo-nutrition-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables assistants and agents to look up sourced nutrition, glycemic load, and micronutrient data for Indian dishes and ingredients by amount in grams or household measures, including meal totals, nutrient rankings, and estimated daily targets.5MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural-language nutrition research for Indian foods, combining a curated knowledge base with hybrid RAG and specialized agents. Provides MCP tools for knowledge search, safe calculations, document retrieval, and optional live web search.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that lets you log meals through Claude (and soon ChatGPT) in plain language, using India's official food composition data (IFCT 2017) plus USDA, enabling accurate calorie and macro tracking for Indian dishes with household units and photo logging.34 npm2AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceProvides intelligent access to the USDA nutrition database through AI assistants, enabling users to search foods, compare nutritional content, find foods high in specific nutrients, and query authoritative nutrition data across 7,146+ food items through natural language.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to resolve Japanese food names to nutrition facts per 100g based on official Japanese food composition data.MIT
- FlicenseAqualityBmaintenanceMCP server for pediatric CKD nutrition and food calculations, enabling energy/protein targets, food nutrient lookup, substitutions, meal summaries, and drug-nutrient interaction checks.8-
TDQS
Scored across 8 tools
The tools split cleanly along resource lines: single food (lookup_food) vs multi-food (compare_foods), product list (list_products) vs single product (get_product) vs side-by-side (compare_products), plus two clearly separate protein calculators (target vs cost). The only mild overlaps are list_products vs compare_products (both surface per-serving macros across products) and lookup_food vs compare_foods when only one food is compared.
Most names follow a verb_noun pattern (lookup_food, compare_foods, search_guides, list_products, get_product, compare_products) and are all snake_case. The two protein tools (protein_target, protein_cost) break the verb-first convention by being noun phrases, a minor but noticeable deviation.
Eight tools is well within the sweet spot and each maps to a distinct job: single lookup, comparison, two calculators, guide search, and a three-tool product sub-surface. Nothing feels padded or redundant.
Product coverage is a full read lifecycle (list/get/compare with live price), but the 59-food database has no list or search-by-name/criteria tool, so an agent must already know exact food names to use lookup_food or compare_foods. search_guides returns titles and URLs only, with no tool to fetch a guide's content, leaving dead ends for citation depth.