# Jecfa (npm · @pipeworx/mcp-jecfa)

JECFA (Joint FAO/WHO Expert Committee on Food Additives) — safety evaluations, Acceptable Daily…

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 64/100, [markdown](https://verifymcp.io/servers/pipeworx-io-jecfa/jecfa-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-jecfa/jecfa-mcp)
- npm · `@pipeworx/mcp-jecfa`: 85/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-jecfa/pipeworx-mcp-jecfa.md), [page](https://verifymcp.io/servers/pipeworx-io-jecfa/pipeworx-mcp-jecfa)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-jecfa`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-jecfa).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 671 tokens (~111/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-jecfa -- npx -y @pipeworx/mcp-jecfa
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-jecfa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jecfa"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-jecfa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jecfa"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-jecfa -- npx -y @pipeworx/mcp-jecfa
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-jecfa": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-jecfa"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-jecfa --command npx --arg -y --arg @pipeworx/mcp-jecfa
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-jecfa:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-jecfa"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-jecfa": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-jecfa"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-jecfa -t stdio -c npx -a -y @pipeworx/mcp-jecfa
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-jecfa": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-jecfa"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, +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.

### 2026-11-03 (score 84, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 69, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 82)

First indexed and scored.

## MCP tools (6)

### `jecfa_search` (~150 tokens)

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.

Input parameters:

- `query` (string, required): Substance name or fragment ("aspartame", "sunset yellow"), CAS number ("22389-47-0"), or INS/E-number ("E951", "951", "160a(iii)").

### `jecfa_chemical` (~121 tokens)

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.

Input parameters:

- `id` (number, required): Chemical id from jecfa_search (e.g. 62 for aspartame).

### `jecfa_by_functional_class` (~134 tokens)

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.

Input parameters:

- `functional_class` (string, required): Class name ("sweetener", "preservative"), group name ("food_additives"), or a numeric class id from jecfa_functional_classes.

### `jecfa_functional_classes` (~78 tokens)

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.

### `jecfa_by_number` (~77 tokens)

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.

Input parameters:

- `number` (string, required): FEMA or JECFA number, e.g. "1" or "2001".

### `jecfa_recent_evaluations` (~57 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-jecfa/pipeworx-mcp-jecfa#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 69
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 82

## Common questions

### 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.

### What did VerifyMCP test on the Jecfa MCP server?

VerifyMCP ran 16 checks on Jecfa, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-jecfa
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-jecfa
- Repository: https://github.com/pipeworx-io/mcp-jecfa
- Website: https://pipeworx.io/packs/jecfa
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-jecfa/pipeworx-mcp-jecfa.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-jecfa/pipeworx-mcp-jecfa/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-jecfa/pipeworx-mcp-jecfa.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-jecfa/pipeworx-mcp-jecfa