Nutrition MCP
REMOTE · DOCUSLIDE-MCP-PRODUCTION.UP.RAILWAY.APP · SCANNED AUG 11
USDA FoodData Central nutrition data: search foods, compare macros, and analyze meals.
Available components
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 →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · docuslide-mcp-production.up.railway.app
claude mcp add --transport http andrewvg23-nutrition-mcp https://docuslide-mcp-production.up.railway.app/mcp
[mcp_servers.andrewvg23-nutrition-mcp] url = "https://docuslide-mcp-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"andrewvg23-nutrition-mcp": {
"type": "remote",
"url": "https://docuslide-mcp-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add andrewvg23-nutrition-mcp --url https://docuslide-mcp-production.up.railway.app/mcp --transport streamable-http
mcp_servers:
andrewvg23-nutrition-mcp:
url: "https://docuslide-mcp-production.up.railway.app/mcp" {
"mcpServers": {
"andrewvg23-nutrition-mcp": {
"type": "http",
"url": "https://docuslide-mcp-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Aug 26 −23
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Aug 26 59
First indexed and scored.
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 11 Aug 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=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
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. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://docuslide-mcp-production.up.railway.app/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://docuslide-mcp-production.up.railway.app/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.", resource_metadata="https://docuslide-mcp-production.up.railway.app/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://docuslide-mcp-production.up.railway.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://docuslide-mcp-production.up.railway.app/mcp |
| Authorisation server | https://docuslide-mcp-production.up.railway.app/ |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docuslide-mcp-production.up.railway.app/mcp | Auth required | 401 | |
| 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.
analyze_meal ~137
Total the nutrition across several foods to analyze a whole meal. Check `failed` and `partial` in the response before reporting totals — a non-empty `failed` list means some items were left out of the sum. Args: items: List of entries, each with an `fdc_id` (int, required) and `grams` (number, defaults to 100). At most 25 items. Example: [{"fdc_id": 173944, "grams": 150}, {"fdc_id": 168462, "grams": 80}]
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_foods ~114
Compare several foods side by side at the same serving weight. Use this for "which has more protein" style questions. Check the `failed` list in the response — if it is non-empty some foods could not be loaded and the comparison is incomplete. Args: fdc_ids: FoodData Central ids to compare, at most 10. grams: Serving weight applied to every food, in grams. Defaults to 100.
| Name | Type | Req | Description |
|---|---|---|---|
| fdc_ids | array | yes | – |
| grams | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_food_nutrition ~123
Get the full nutrient breakdown for one food at a given serving weight. Returns macros, micronutrients, percent daily values, and a list of common portion sizes with their gram weights — use those to convert a user's "1 cup" or "1 medium" into the grams argument on a follow-up call. Args: fdc_id: The food's FoodData Central id, from search_foods. grams: Serving weight in grams. Defaults to 100.
| Name | Type | Req | Description |
|---|---|---|---|
| fdc_id | integer | yes | – |
| grams | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_foods ~188
Search the USDA food database by name and return matching foods. Always call this first to resolve a food name into an fdc_id — the other tools need that id. Results include key macros per 100g so you can often answer simple questions without a follow-up call. Args: query: Food name to search for, e.g. "raw spinach" or "cheddar cheese". limit: Maximum results to return, 1-50. Defaults to 10. data_type: Restrict to one USDA dataset. "Foundation" and "SR Legacy" are whole/unbranded foods with the highest quality data; "Branded" covers packaged supermarket products; "Survey (FNDDS)" covers prepared dishes. Omit to search all.
| Name | Type | Req | Description |
|---|---|---|---|
| data_type | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.