io.github.rootsbymenda/food-safety
REMOTE · FOOD-MCP-SERVER.ROOTSBYBENDA.WORKERS.DEV · 2 COMPONENTS
Food additive safety: JECFA, EFSA, ADI, halal/kosher/vegan. 6K+ additives. Free.
Last scanned (39 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared sse, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.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.
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.
- 28 Sept 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
- 25 Sept 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
- 26 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
- 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
- 4 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.27 → unverified ▼ security
- HTTPS: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Aug 26 0
- Transport: fail → pass ▲ security
- 31 Jul 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
- 27 Jul 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
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 5 Nov 2026 · Probed https://food-mcp-server.rootsbybenda.workers.dev/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rootsbybenda.workers.dev | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 15355523f9dba24913c1d5d4dc380a04 |
| SANs: rootsbybenda.workers.dev, *.rootsbybenda.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of food-mcp-server.rootsbybenda.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://food-mcp-server.rootsbybenda.workers.dev/sse | HTTP error | 404 | |
| http (plaintext) | http://food-mcp-server.rootsbybenda.workers.dev/sse | Inconclusive | 404 |
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 →
check_additive ~329
Retrieve food additive safety data including toxicological evaluations, regulatory status, and dietary compatibility from 6,450 food additive records. Input: additive common name, E-number, or CAS number (e.g. 'aspartame', 'E951', '22839-47-0'). Returns: safety score (1-10 scale), ADI (Acceptable Daily Intake) with source, JECFA evaluation history (ADI status, functional class, evaluation year), EFSA toxicology data (ADI/TDI/NOAEL values, genotoxicity), EU and US regulatory status, Israel MOH permitted-additive status, IARC classification, health concerns, allergen flags, dietary compatibility (vegan, halal, kosher, diabetic), PubChem chemistry data, common foods, and banned-country list. Sources: JECFA (6,563 evaluations), EFSA (5,251 substances), EU food additive regulations, US FDA GRAS, Israel MOH, IARC. For food additive safety assessment and regulatory compliance. Do not use for full ingredient-list scans (use check_ingredient_list), nutrition queries (use check_nutrition), or pesticide MRLs (use check_pesticide_mrl).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Food additive common name (e.g. 'aspartame'), E-number used in EU-style food labeling (e.g. 'E951'), INS number where applicable, or CAS number (Chemical Abstracts Service registry number, e.g. '2283… |
No output schema declared.
No examples provided.
check_ingredient_list ~305
Scan a packaged-food product ingredient list for additive safety risks, regulatory compliance, allergens, and dietary compatibility across target markets. Input: comma-separated ingredient list as printed on food packaging (up to 60 ingredients). Returns per-ingredient: matched additive name, E-number, safety score (1-10), category, EU/US status, health concerns, allergen flags, and ADI. Returns overall: LOW/MODERATE/HIGH risk assessment, average safety score, flagged high-risk additives with reasons and banned-country data, allergen warnings, and market-specific compliance notes. Database: 6,450+ food additives with 77,278 synonyms for fuzzy matching. For food product safety screening and market compliance. Do not use for single additive lookup (use check_additive), nutrition facts (use check_nutrition), or pesticide MRLs (use check_pesticide_mrl).
| Name | Type | Req | Description |
|---|---|---|---|
| ingredients | string | yes | Comma-separated or newline-separated packaged-food ingredient list exactly as it appears on a label (e.g. 'Water, Sugar, Citric Acid, Sodium Benzoate, Aspartame'). Include additives, colors, preserva… |
| market | string | – | Optional target food regulatory market for compliance focus. Use 'EU', 'US', or 'Israel' when the user asks about a specific market; omit for the default EU + US scan. |
No output schema declared.
No examples provided.
check_nutrition ~250
Retrieve Israeli Ministry of Health official nutrition data for a food item by name in Hebrew or English. Input: food name (e.g. 'hummus', 'chicken breast', 'bread', or Hebrew equivalent). Returns per 100g: energy (kcal), protein, total fat, carbohydrates, dietary fiber, total sugars, alcohol, moisture; vitamins (A, C, E, D, K, B6, B12, thiamin, riboflavin, niacin, folate); minerals (calcium, iron, magnesium, phosphorus, zinc, selenium, sodium, potassium, choline); fats (cholesterol, saturated, mono/polyunsaturated, trans). Source: Israel Ministry of Health Nutrition Database (4,624 food items). For nutritional analysis and dietary reference. Do not use for additive safety (use check_additive) or pesticide MRLs (use check_pesticide_mrl).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Food name in Hebrew or English for Israeli Ministry of Health nutrition lookup (e.g. 'hummus', 'chicken breast', 'bread'). Use a specific food item rather than an additive, crop, or supplement. |
No output schema declared.
No examples provided.
check_pesticide_mrl ~226
Check Israeli official pesticide Maximum Residue Limits (MRL) by pesticide active substance, crop, or pesticide-crop pair. Input: pesticide name, crop name, or combined query in Hebrew or English (e.g. 'glyphosate', 'tomato', 'chlorpyrifos apple'). Returns: active substance, crop (Hebrew and English), official MRL value in mg/kg (ppm), last update date, and pending regulatory changes. Source: Israel Ministry of Health Pesticide Residue Limits (3,708 pesticide-crop MRL records). For agricultural compliance and food safety residue assessment. Do not use for food additive safety (use check_additive), cannabis pesticide limits, or non-Israeli MRL regimes.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Pesticide active substance, crop name, or pesticide-plus-crop phrase for Israeli MRL lookup (e.g. 'glyphosate', 'tomato', 'chlorpyrifos apple'). Use crop/pesticide pairs when the requested residue li… |
No output schema declared.
No examples provided.
search_additives ~354
Search food additive records by keyword, function, category, dietary filter, or health concern for additive discovery and selection. Input: food additive keyword (e.g. 'preservative', 'sweetener', 'hyperactivity', 'banned', 'E1') with optional filter (high_risk, allergens, banned, not_vegan, not_halal). Returns: matching additive names, E-numbers, CAS numbers, Hebrew names, categories, functions, safety scores (1-10), EU/US status, health concerns, allergen flags, dietary status (vegan/halal/kosher), and ADI values. Database: 6,450+ food additives searchable by name, function, category, and Hebrew name. For food additive discovery and category exploration. Do not use when the user has an exact additive name/E-number for full safety data (use check_additive).
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Optional food-additive filter. Use 'high_risk' for elevated safety scores, 'allergens' for allergen-linked additives, 'banned' for restricted/banned signals, 'not_vegan' for animal-derived concerns,… |
| limit | number | – | Maximum number of additive records to return (1-25, default 10). Use higher limits for broad classes like preservatives and lower limits for exact additive names. |
| query | string | yes | Food additive keyword, function, category, dietary status, or concern (e.g. 'preservative', 'sweetener', 'hyperactivity', 'banned', 'E1'). Use broad terms for discovery and exact additive names/E-num… |
No output schema declared.
No examples provided.
How do I install the io.github.rootsbymenda/food-safety MCP server?
io.github.rootsbymenda/food-safety is a hosted endpoint at https://food-mcp-server.rootsbybenda.workers.dev/sse, 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 · food-mcp-server.rootsbybenda.workers.dev
claude mcp add --transport http rootsbymenda-food-safety 'https://food-mcp-server.rootsbybenda.workers.dev/sse'
What is the io.github.rootsbymenda/food-safety MCP server?
io.github.rootsbymenda/food-safety is an MCP server listed in the public MCP registry as io.github.rootsbymenda/food-safety. Food additive safety: JECFA, EFSA, ADI, halal/kosher/vegan. 6K+ additives. Free. This page covers its hosted endpoint (https://food-mcp-server.rootsbybenda.workers.dev/sse).
Is the io.github.rootsbymenda/food-safety MCP server safe to use?
io.github.rootsbymenda/food-safety scores 18 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 io.github.rootsbymenda/food-safety MCP server expose?
io.github.rootsbymenda/food-safety exposes 5 tools: check_additive, check_ingredient_list, search_additives, check_nutrition, check_pesticide_mrl. Their descriptions and schemas cost roughly 1,464 tokens of context every time the server is loaded.
Does the io.github.rootsbymenda/food-safety MCP server require authentication?
Its publisher declares no required credentials for io.github.rootsbymenda/food-safety. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.rootsbymenda/food-safety MCP server still maintained?
io.github.rootsbymenda/food-safety is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.