Jecfa
NPM · @PIPEWORX/MCP-JECFA · 2 COMPONENTS
JECFA (Joint FAO/WHO Expert Committee on Food Additives) — safety evaluations, Acceptable Daily…
Available components
Last scanned (8 hours ago)
Scores higher than 87% 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-jecfa). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 671 tokens (~111/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 4 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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 82
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-jecfa@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-jecfa |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-jecfa/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649449586 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bc295b960a7eb72b2820d92f2d2180383e8c14ae5b570bb1895f4de595a2431ba1331385985a366719149e4add1bb0ea05863ec6112360a31d6c82899 |
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 →
jecfa_by_functional_class ~134
List every substance JECFA has evaluated in one functional class — sweeteners, preservatives, colours, emulsifiers, antioxidants and so on — or every substance in one of the four groups: food_additives, flavouring_agents, food_contaminants, veterinary_drugs. Each entry carries its ADI and CAS number. Use to survey what is permitted in a category rather than to look up a single substance.
| Name | Type | Req | Description |
|---|---|---|---|
| functional_class | string | yes | Class name ("sweetener", "preservative"), group name ("food_additives"), or a numeric class id from jecfa_functional_classes. |
No output schema declared.
No examples provided.
jecfa_by_number ~77
Resolve a FEMA number or a JECFA substance number to its evaluated substance. These identifiers appear in flavouring literature and JECFA meeting reports. For INS/E-numbers use jecfa_search instead.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | FEMA or JECFA number, e.g. "1" or "2001". |
No output schema declared.
No examples provided.
jecfa_chemical ~121
Fetch the complete JECFA record for one substance by its chemical id: chemical and synonym names, CAS and INS numbers, functional class, and every safety evaluation JECFA has made of it — evaluation year, ADI, the committee’s conclusions, dietary exposure findings, meeting number, and the TRS report and toxicological monograph citations. Use after search to explain how and when an ADI was set or revised.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Chemical id from jecfa_search (e.g. 62 for aspartame). |
No output schema declared.
No examples provided.
jecfa_functional_classes ~78
List the JECFA functional-class vocabulary — the 71 technological purposes a substance can be evaluated under (sweetener, emulsifier, antioxidant, humectant…), grouped into food additives, flavouring agents, food contaminants and veterinary drugs. Call this to discover the exact class name that jecfa_by_functional_class expects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jecfa_recent_evaluations ~57
Show the substances most recently added or re-evaluated by JECFA, with their current ADI and functional class. Use to check what the committee has looked at lately rather than to look up a known substance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jecfa_search ~150
Look up a food additive, flavouring, contaminant or veterinary drug in the WHO/FAO JECFA database by substance name, CAS number, or INS/E-number (E951, INS 951, 160a). Returns the Acceptable Daily Intake (ADI), CAS number, functional class and a chemical id for fetching the full safety evaluation. Use this to answer whether a substance has been evaluated for safety and what intake level was judged acceptable.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Substance name or fragment ("aspartame", "sunset yellow"), CAS number ("22389-47-0"), or INS/E-number ("E951", "951", "160a(iii)"). |
No output schema declared.
No examples provided.
How do I install the Jecfa MCP server?
Jecfa runs locally as an npm package, launched with npx -y @pipeworx/mcp-jecfa. 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-jecfa
claude mcp add pipeworx-io-jecfa -- npx -y @pipeworx/mcp-jecfa
What is the Jecfa MCP server?
Jecfa is an MCP server listed in the public MCP registry as io.github.pipeworx-io/jecfa. JECFA (Joint FAO/WHO Expert Committee on Food Additives), safety evaluations, Acceptable Daily… This page covers its npm package (@pipeworx/mcp-jecfa).
Is the Jecfa MCP server safe to use?
Jecfa scores 85 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 Jecfa MCP server expose?
Jecfa exposes 6 tools: jecfa_search, jecfa_chemical, jecfa_by_functional_class, jecfa_functional_classes, jecfa_by_number, jecfa_recent_evaluations. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.
Is the Jecfa MCP server still maintained?
Jecfa 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 Jecfa MCP server under?
Jecfa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.