Allergen Detector
REMOTE · ALLERGEN-DETECTOR-MCP.ONRENDER.COM
Checks food and cosmetic ingredients against each household member's allergies, incl. hidden names.
Available components
Last scanned (2 hours ago)
Scores higher than 66% 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 479 tokens (~159/item across 3 items; 3 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 Management33
- Stability observed for 10 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 5 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.
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- “check_product_allergens” added an optional parameter “language” cosmetic
- “lookup_ingredient” added an optional parameter “language” cosmetic
- 1 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.
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_product_allergens” rewrote its description, which is the text the model reads security
- Schema quality: 99 → 131 ▼ functional
- 30 Oct 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.
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_product_allergens” rewrote its description, which is the text the model reads security
- Schema quality: 117 → 99 ▲ functional
- 28 Oct 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.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ 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://allergen-detector-mcp.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| 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 allergen-detector-mcp.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | 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://allergen-detector-mcp.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://allergen-detector-mcp.onrender.com/mcp | HTTPS enforced | 301 | https://allergen-detector-mcp.onrender.com/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 →
check_product_allergens Check a product for allergens ~206
Check a product's ingredient list against the allergies of one or more people in a household. Catches allergens listed under other names (e.g. "arachis oil" for peanut, "casein" for milk, Latin plant names in cosmetics) and does not let "free from" claims hide a real ingredient. Covers food and cosmetics. Use when the user asks if a product or ingredient list is safe for someone with allergies. A result with no listed allergens is not a promise of safety: relay the limits, and never call the product "safe".
| Name | Type | Req | Description |
|---|---|---|---|
| household | array | yes | One entry per person, each with their allergens. |
| ingredients | string | yes | The product's ingredient list, or the product page text that contains it. |
| language | string | – | Language of the text, if known, e.g. "fr". Optional; helps short words in other languages be read correctly. |
| product_name | string | – | Product name, for the answer only. |
No output schema declared.
No examples provided.
list_supported_allergens List supported allergens ~32
List the allergens this service can check (food and cosmetic), with the other names users may type for them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_ingredient Look up an ingredient ~112
Tell which allergens, if any, an ingredient name belongs to, e.g. "sodium caseinate" -> milk, "Prunus amygdalus dulcis oil" -> tree nuts, "DMDM hydantoin" -> formaldehyde releasers.
| Name | Type | Req | Description |
|---|---|---|---|
| ingredient | string | yes | One ingredient name as printed on a label. |
| language | string | – | Language of the text, if known, e.g. "fr". Optional; helps short words in other languages be read correctly. |
No output schema declared.
No examples provided.
How do I install the Allergen Detector MCP server?
Allergen Detector is a hosted endpoint at https://allergen-detector-mcp.onrender.com/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 · allergen-detector-mcp.onrender.com
claude mcp add --transport http daniellemeng1022-allergen-detector 'https://allergen-detector-mcp.onrender.com/mcp'
What is the Allergen Detector MCP server?
Allergen Detector is an MCP server listed in the public MCP registry as io.github.daniellemeng1022/allergen-detector. Checks food and cosmetic ingredients against each household member's allergies, incl. hidden names. This page covers its hosted endpoint (https://allergen-detector-mcp.onrender.com/mcp).
Is the Allergen Detector MCP server safe to use?
Allergen Detector scores 76 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 Allergen Detector MCP server expose?
Allergen Detector exposes 3 tools: check_product_allergens, lookup_ingredient, list_supported_allergens. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Does the Allergen Detector MCP server require authentication?
No. We connected to Allergen Detector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Allergen Detector MCP server still maintained?
Allergen Detector 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.