Openfoodtox
NPM · @PIPEWORX/MCP-OPENFOODTOX · 2 COMPONENTS
EFSA OpenFoodTox — the reference values EFSA has derived for chemical substances in food and feed…
Available components
Last scanned (13 hours ago)
Scores higher than 76% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-openfoodtox). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 335 tokens (~167/item across 2 items; 2 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 Management23
- Stability observed for 7 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.20 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-openfoodtox@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-openfoodtox |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-openfoodtox/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685109532 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cc98481ef41677cec9a677f504ea5fa8e9e3296bf822a61573e4870e18cb6e308959d64eeefa1db616d4c381a758d1c0a5d86be10649f3142e2368798 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
openfoodtox_hazard_profile ~184
Get EFSA's derived toxicological reference values for a chemical substance in food or feed — acceptable daily intake (ADI), acute reference dose (ARfD), tolerable intakes, and operator exposure levels — each with the assessment body that set it and the critical endpoint it was based on. Use for questions like "what is the ADI for glyphosate" or "what tolerable intake has EFSA set for cadmium". Covers 3,437 substances that have at least one reference value, from EFSA OpenFoodTox 3.0.
| Name | Type | Req | Description |
|---|---|---|---|
| substance | string | yes | Chemical or substance name, e.g. "glyphosate", "aspartame", "cadmium", "deoxynivalenol". Matched case-insensitively; a partial name resolves to the closest substance and the response says which. |
No output schema declared.
No examples provided.
openfoodtox_search ~97
Search EFSA OpenFoodTox for assessed substances by name fragment, returning each match with how many reference values it carries. Use to find the exact substance name before requesting a hazard profile, or to see which related compounds EFSA has assessed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum matches to return (default 20). |
| query | string | yes | Name fragment, e.g. "aflatoxin" or "phthalate". |
No output schema declared.
No examples provided.
How do I install the Openfoodtox MCP server?
Openfoodtox runs locally as an npm package, launched with npx -y @pipeworx/mcp-openfoodtox. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-openfoodtox
claude mcp add pipeworx-io-openfoodtox -- npx -y @pipeworx/mcp-openfoodtox
What is the Openfoodtox MCP server?
Openfoodtox is an MCP server listed in the public MCP registry as io.github.pipeworx-io/openfoodtox. EFSA OpenFoodTox, the reference values EFSA has derived for chemical substances in food and feed… This page covers its npm package (@pipeworx/mcp-openfoodtox).
Is the Openfoodtox MCP server safe to use?
Openfoodtox scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Openfoodtox MCP server expose?
Openfoodtox exposes 2 tools: openfoodtox_hazard_profile, openfoodtox_search. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.
Is the Openfoodtox MCP server still maintained?
Openfoodtox 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.
What licence is the Openfoodtox MCP server under?
Openfoodtox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Openfoodtox MCP server?
VerifyMCP ran 16 checks on Openfoodtox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.