Skip to main content
Glama
seraphinerenard

usda-fdc-mcp

by seraphinerenard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to usda-fdc-mcp

No user-submitted related servers found.

    Related Servers

    • foodmcp

      carleshub
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for cooking and recipe management powered by Spoonacular API. Enables natural-language recipe search, ingredient-based discovery, nutrition breakdowns, and ingredient substitutions.
      -

    • openfoodfacts-mcp

      domdomegg
      A
      license
      A
      quality
      B
      maintenance
      An MCP server for the Open Food Facts API that allows users to search, read, and contribute to a global food database. It enables looking up nutrition data by barcode or name and managing product information through natural language.
      10
      28 npm
      3
      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
    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

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct role: get_food for known IDs, search_foods for discovery, food_nutrition for a name-based shortcut with nutrients, and recipe_nutrition for multi-ingredient calculations. However, the overlap between food_nutrition and search_foods/get_food could cause some initial confusion, but descriptions clarify the intended use.

    Naming Consistency3/5

    Names mix verb_noun (get_food, search_foods) and noun_noun (food_nutrition, recipe_nutrition) patterns, which is inconsistent and less predictable. The mixed conventions make it harder to infer a tool's function from its name alone.

    Tool Count5/5

    Four tools is well-scoped for a USDA food data server, covering search, ID-based lookup, convenience queries, and recipe analysis. Each tool earns its place without unnecessary bloat.

    Completeness5/5

    The surface covers the core workflow of finding a food, retrieving its nutrients, and combining foods into recipes. For a read-only database, there are no obvious gaps or dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources