Usda Fdc
Server Details
USDA Food Data Central MCP
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 37.3% over 38 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-usda-fdc
- GitHub Stars
- 0
- Server Listing
- mcp-usda-fdc
TDQS
Scored across 36 tools
The set contains several overlapping families: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all route questions; discover_tools and suggest_questions both reveal capabilities; and polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and polymarket_kalshi_spread overlap heavily around prediction-market analysis. Detailed descriptions reduce but do not eliminate misselection risk, especially since ask_pipeworx_beta currently duplicates ask_pipeworx.
All tool names use snake_case consistently, with no camelCase or punctuation drift. The main variation is verb-first versus noun-first phrasing (e.g., list_foods vs entity_profile, polymarket_edges), but the convention remains predictable.
36 tools is in the excessive 25+ range and includes redundant meta-variants such as ask_pipeworx_beta alongside multiple Polymarket scanners. For a server labeled Usda Fdc, this is a substantial scope mismatch; even as a broad Pipeworx gateway it feels heavy and partially duplicative.
For USDA FoodData Central, the surface covers search, browse, food-group listing, full record retrieval, and nutrient extraction, which is adequate for a read-only reference API. The broader Pipeworx tool set is also wide-ranging, though the combination leaves the server without a single coherent domain to fully complete.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
Related MCP Connectors
USDA FoodData Central nutrition data: search foods, compare macros, and analyze meals.
FAS MCP — USDA Foreign Agricultural Service (trade & global production data)
USDA FoodData Central nutrient lookup, FDA recall watch, EU FMCG labelling via remote MCP
Search foods, compare nutrients, and look up the full USDA FoodData Central database.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables searching USDA foods, comparing nutrients, and accessing the full FoodData Central database via MCP tools and resources.212 npm1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides access to USDA FoodData Central database, enabling food search, nutrition details, and comparison for dietary analysis via MCP.5-
- FlicenseAqualityCmaintenanceMCP server that provides food composition data from USDA FoodData Central, enabling search, nutrient lookups, and recipe nutrition calculations.4-
- AlicenseNot gradedqualityDmaintenanceMCP server for USDA nutrition data lookup, meal logging, and daily macro tracking.51 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.