Nutriscan MCP connector
Related Servers
Alternatives to Nutriscan MCP connector
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables natural language access to USDA's FoodData Central database with 1M+ foods, supporting search, nutrition facts, food comparison, and daily value calculations.8MIT
- FlicenseNot gradedqualityDmaintenanceEnables logging food into MyFitnessPal diary via natural language, supporting search, log, quick add, and diary retrieval.-
- AlicenseNot gradedqualityCmaintenanceEnables tracking food intake and nutrition using the USDA FoodData Central database. Supports logging meals, setting daily nutrition goals, viewing food diaries, and analyzing nutrition trends over time with local SQLite storage.7 npm1MIT
- AlicenseNot gradedqualityCmaintenanceProvides access to a comprehensive food database with 300,000+ items, enabling nutritional data lookups, food searches, and barcode scanning with all processing happening locally for privacy and speed.211MIT
- AlicenseBqualityBmaintenanceEnables querying a global food nutrition database of generic and branded products, including search by name, lookup by barcode, and retrieval of resolved nutrient values pinned to a dated snapshot. Coverage spans USDA FoodData Central and Open Food Facts sources, with freshness health checks available.9AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceEnables agents to log and edit meals, query a food journal, and retrieve calorie/macro/quality KPIs with server-side nutritional grading, plus manage staples and targets.1-
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.