Nutrition MCP
REMOTE · DOCUSLIDE-MCP-PRODUCTION.UP.RAILWAY.APP
USDA FoodData Central nutrition data: search foods, compare macros, and analyze meals.
Available components
Last scanned (17 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
Recent critical change
Authorization (10 Nov 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (set_profile). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2017 tokens (~144/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.2.1 → 0.2.2 functional
- 10 Nov 26 +27
- Authorization: pass → fail ▼ critical
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “clear_profile”, which the server declares destructive security
- New tool “set_profile”, which the server declares destructive security
- Tool “find_foods_by_nutrient” rewrote its description, which is the text the model reads security
- Tool “analyze_meal” rewrote its description, which is the text the model reads security
- Tool “compare_foods” rewrote its description, which is the text the model reads security
- Tool “get_food_nutrition” rewrote its description, which is the text the model reads security
- Tool “search_foods” rewrote its description, which is the text the model reads security
- Schema quality: 636 → 2017 ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Schema quality: 159 → 140 ▲ functional
- Tool coverage: 0% → 100% ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- The server no longer declares the “experimental” capability functional
- The server no longer declares the “prompts” capability functional
- The server no longer declares the “resources” capability functional
- First check of Destructive annotations: 100 functional
- Schema quality: excellent → good functional
- Server version: 0.2.0 → 0.2.1 functional
- Server version: 2.14.7 → 0.2.0 functional
- New tool “list_retailers” functional
- New tool “get_profile” functional
- New tool “analyze_plan” functional
- New tool “analyze_recipe” functional
- New tool “database_status” functional
- New tool “find_foods_by_nutrient” functional
- New tool “prepare_retailer_handoff” functional
- New tool “resolve_ingredients” functional
- “search_foods” added an optional parameter “offset” cosmetic
- “analyze_meal” reworded the description of “items” cosmetic
- “compare_foods” reworded the description of “fdc_ids” cosmetic
- “compare_foods” reworded the description of “grams” cosmetic
- “get_food_nutrition” reworded the description of “fdc_id” cosmetic
- “get_food_nutrition” reworded the description of “grams” cosmetic
- “search_foods” reworded the description of “data_type” cosmetic
- “search_foods” reworded the description of “limit” cosmetic
- “search_foods” reworded the description of “query” cosmetic
- Tool “analyze_meal” changed its title: Analyze a meal cosmetic
- Tool “compare_foods” changed its title: Compare foods cosmetic
- Tool “get_food_nutrition” changed its title: Food nutrients cosmetic
- Tool “search_foods” changed its title: Search foods cosmetic
- 7 Nov 26 0
- Endpoint reachability: unreachable → behind authorisation ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://docuslide-mcp-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of docuslide-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docuslide-mcp-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://docuslide-mcp-production.up.railway.app/mcp | HTTPS enforced | 301 | https://docuslide-mcp-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_meal Analyze a meal ~122
Totals nutrients across several foods and assesses the meal. assessment.shortfalls lists missed targets, worst first, and assessment.over_limit lists exceeded limits. not_reported lists nutrients with no data in the food records; those are unknown, not zero. failed lists items left out of the total, and partial is true when there are any.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Foods in the meal, 1-25, each an fdc_id with grams, e.g. [{"fdc_id": 168462, "grams": 150}]. |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_plan Analyze a meal plan ~225
Analyzes a multi-day meal plan and assesses its daily average. Every ingredient is resolved and converted, then totaled by dish, meal, and day, up to 400 ingredients. The assessment is of the daily average, not the multi-day sum. per_day has each day's totals, shopping_list totals ingredients at full recipe quantities, and failed lists ingredients missing from the totals. The detail breakdown is large for a full week.
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | yes | Days, 1-14, each {"day": "Monday", "meals": [{"name": "dinner", "dishes": [...]}]}. A dish is {"name": "Moussaka", "servings": 6, "eaten": 1, "ingredients": [...]}, where servings is the recipe yield… |
| detail | boolean | – | Include the per-dish, per-ingredient breakdown. Defaults to false. |
| include_shopping_list | boolean | – | Include total ingredient quantities to buy. Defaults to true. |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_recipe Analyze a recipe ~133
Totals one dish from its ingredient list and reports it per serving. Ingredient quantities are for the whole dish, as a recipe states them. per_serving divides by servings, whole_recipe holds the undivided totals, and the assessment covers one serving.
| Name | Type | Req | Description |
|---|---|---|---|
| ingredients | array | yes | Ingredients, each with a food name or fdc_id and a portion or grams, e.g. {"food": "eggplant", "portion": "2 medium"}. |
| name | string | yes | Dish name, e.g. Moussaka. |
| servings | number | – | Servings the recipe yields. Defaults to 1. |
Structured output declared, but exposes no named fields.
No examples provided.
clear_profile Clear profile ~32
Deletes this conversation's profile so assessments use the FDA food-label values. cleared is false when no profile was set.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
compare_foods Compare foods ~96
Puts several foods side by side at the same serving weight. highest_per_nutrient names the food with the most of each nutrient. failed lists ids that could not be loaded, and partial is true when the comparison is missing some of them.
| Name | Type | Req | Description |
|---|---|---|---|
| fdc_ids | array | yes | FoodData Central ids to compare, 1-10. |
| grams | number | – | Serving weight in grams. Defaults to 100. |
Structured output declared, but exposes no named fields.
No examples provided.
database_status Database status ~34
Reports whether the local USDA database is built and what it holds. The result counts foods by dataset and records with an ingredient statement.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
find_foods_by_nutrient Rank foods by nutrient ~258
Ranks foods by how much of one nutrient they carry per 100 g. The default list is lab-measured foods. Branded products are included only when data_type is Branded. Amounts that cannot fit in 100 g, and potassium above the potassium-chloride ceiling, are left out. Per-100 g ranking favors foods eaten in small amounts, such as spices and dried herbs; the category filter narrows the list to one food group. Results are paged, and pagination.next_offset is null on the last page.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | USDA food category, matched as a substring, e.g. Vegetables or Legumes. |
| data_type | – | – | One USDA dataset. Foundation and SR Legacy are unbranded whole foods, Branded is packaged products, and Survey (FNDDS) is prepared dishes. Omitted, all four are searched. |
| limit | integer | – | Results per page, 1-100. Defaults to 20. |
| min_amount | – | – | Minimum amount per 100 g. |
| nutrient | string | yes | Nutrient to rank by. |
| offset | integer | – | Results to skip, from pagination.next_offset. Defaults to 0. |
Structured output declared, but exposes no named fields.
No examples provided.
get_food_nutrition Food nutrients ~135
Returns the nutrient breakdown for one food at a serving weight. The result has macros, micronutrients, an assessment against daily targets, USDA's verbatim ingredient statement when available, and common portion sizes with their gram weights. ingredients_available is false when USDA supplied no ingredient statement, which does not mean the food has no ingredients. assessment.basis is personal_dri when a profile is set and fda_label_dv otherwise.
| Name | Type | Req | Description |
|---|---|---|---|
| fdc_id | integer | yes | FoodData Central id from search_foods. |
| grams | number | – | Serving weight in grams. Defaults to 100. |
Structured output declared, but exposes no named fields.
No examples provided.
get_profile Show profile ~41
Returns this conversation's profile and the daily targets it resolves to. profile is null when none is set, and assessments then use the FDA food-label daily values.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_retailers List retailers ~47
Lists configured retailers and the commerce capabilities each supports. A retailer with integration_mode link_handoff supports product links only; no account, cart, checkout, or order is created for it.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
prepare_retailer_handoff Prepare product links ~139
Packages exact retailer products into links for the user to open. The handoff repeats the products, links, and quantities with the original request. It does not contact the retailer, change a cart, or check out.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Exact products, 1-50, each with the retailer's product_id, a name, an absolute HTTPS product_url, and a positive quantity. |
| original_request | string | yes | The shopping request the products were chosen for. |
| retailer_id | string | yes | Retailer id from list_retailers. |
| store_id | – | – | Retailer store or location id, if known. |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_ingredients Resolve ingredients ~191
Matches ingredient names to FoodData Central foods and converts portions to grams. Portions such as 2 tbsp, 1/2 cup, or 1 medium are converted with each food's own measured portions, so 1 cup differs for spinach and olive oil. Repeated ingredients are looked up once. method says how each portion was converted. Ingredients that could not be converted are listed under unresolved with the portions that food supports, and alternatives lists runner-up matches with their fdc_id. Bare names such as rice or beans match many records; names with the cooked state, such as cooked white rice, match more precisely. About a fifth of USDA foods have a portion table.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Ingredients, each with a food name or fdc_id and a portion or grams, e.g. {"food": "eggplant", "portion": "2 medium"}. |
Structured output declared, but exposes no named fields.
No examples provided.
search_foods Search foods ~186
Searches USDA FoodData Central by food name. Each match has an fdc_id, its dataset, key macros per 100 g, and, for branded products, USDA's verbatim ingredient statement. ingredients_available is false when USDA supplied no ingredient statement for that record. Results are paged, and pagination.next_offset is null on the last page.
| Name | Type | Req | Description |
|---|---|---|---|
| data_type | – | – | One USDA dataset. Foundation and SR Legacy are unbranded whole foods, Branded is packaged products, and Survey (FNDDS) is prepared dishes. Omitted, all four are searched. |
| limit | integer | – | Results per page, 1-50. Defaults to 10. |
| offset | integer | – | Results to skip, from pagination.next_offset. Defaults to 0. |
| query | string | yes | Food name, e.g. raw spinach or cheddar cheese. |
Structured output declared, but exposes no named fields.
No examples provided.
set_profile Set profile ~195
Stores a profile for this conversation so assessments use Dietary Reference Intakes. Age- and sex-specific U.S. Dietary Reference Intakes replace the generic food-label values. The result lists the resolved daily targets and limits. The profile is held in memory for the conversation, replaces any earlier profile, and is not written to disk.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | Activity level, used only for the calorie estimate. Defaults to moderate. |
| age | integer | yes | Age in years, 1-120. |
| height_cm | – | – | Height in centimeters; with weight_kg, adds a calorie estimate and the saturated-fat and sugar limits derived from it. |
| life_stage | string | – | Pregnancy and lactation apply only with sex female. Defaults to none. |
| sex | string | yes | Sex that selects the reference values. |
| weight_kg | – | – | Body weight in kilograms; adds a 0.8 g/kg protein target. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Nutrition MCP server?
Nutrition MCP is a hosted endpoint at https://docuslide-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · docuslide-mcp-production.up.railway.app
claude mcp add --transport http andrewvg23-nutrition-mcp 'https://docuslide-mcp-production.up.railway.app/mcp'
What is the Nutrition MCP server?
Nutrition MCP is listed in the public MCP registry as io.github.AndrewVG23/nutrition-mcp. USDA FoodData Central nutrition data: search foods, compare macros, and analyze meals. This page covers its hosted endpoint (https://docuslide-mcp-production.up.railway.app/mcp).
Is the Nutrition MCP server safe to use?
Nutrition MCP scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Nutrition MCP server expose?
Nutrition MCP exposes 14 tools: search_foods, get_food_nutrition, compare_foods, analyze_meal, find_foods_by_nutrient, and 9 more. Their descriptions and schemas cost roughly 1,834 tokens of context every time the server is loaded.
Does the Nutrition MCP server require authentication?
No. We connected to Nutrition MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nutrition MCP server still maintained?
Nutrition MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Nutrition MCP server?
VerifyMCP ran 13 checks on Nutrition MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.