Skip to main content
Glama
SpyrosBou

USDA FoodData Central MCP Server

by SpyrosBou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to USDA FoodData Central MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-usda-fdc

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools to search and retrieve USDA Food Data Central information, including food items, nutrients, and food groups, enabling AI agents to query food data through natural language.
      1 npm
      MIT

    • usda-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching USDA foods, comparing nutrients, and accessing the full FoodData Central database via MCP tools and resources.
      211 npm
      1
      Apache 2.0

    • Food Data Central MCP Server

      FelipeAdachi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to search the USDA's FoodData Central database and retrieve detailed nutritional information and ingredient lists. It supports comprehensive food data access through keyword searches and structured queries for specific food items.
      3
      MIT

    • USDA Nutrition Database MCP

      HemantaPatil
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides 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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation3/5

    Several tools return overlapping nutrient data (e.g., get_macros, get_macro_micros, and individual get_kcal/get_protein/get_carbs/get_fats), which could lead an agent to select a broader or narrower result than needed. Descriptions are specific enough to disambiguate most cases, but the set is not fully distinct.

    Naming Consistency2/5

    Tool names mix kebab-case (list-foods, search-foods, get-food, get-foods) with snake_case (get_macros, list_portions, macros_for_portion), violating the consistency rule. All use a verb_noun structure, but the hyphen/underscore split is unpredictable.

    Tool Count3/5

    16 tools is at the edge of the comfortable range, and the many single-nutrient getters (get_kcal, get_protein, get_carbs, etc.) inflate the count without adding truly distinct capabilities. Still, the core search/lookup/portion workflows justify most of the tools.

    Completeness4/5

    For a read-only food database, the server covers discovery (search/list), retrieval (get-food/get-foods), nutrient breakdowns, and portions. No obvious dead ends; minor gaps like per-food-specific nutrient filtering for raw values are not needed since get-food supports nutrient subsets.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources